Claudify

---

name: claudify metadata: author: es6kr version: "0.1.2" depends-on: [skill-kit] description: Convert functionality into Claude Code automation. Includes interactive supervisor agent pattern (see resources/agent-templates.md §7). Use when the user says "agentify", "agentic", "automate this", "create an agent", "make a plugin", "make a skill", "interactive agent", "supervisor pattern", or wants to automate a workflow as an agent, skill, or plugin. allowed-tools: - Read - Write - Edit - Glob - Skill - Bash(mkdir:*)

---

Claudify

Guide users to convert functionality into the appropriate Claude Code automation type (Agent, Skill, Rule, Command, or Hook).

Decision Matrix

| Type | When to use | Implementation | | ---- | ----------- | -------------- | | Agent | High autonomy, multi-tool | .claude/agents/name.md | | Skill | Domain expertise, logic | .claude/skills/name/SKILL.md | | Rule | Constraints, styling | .claude/rules/name.md | | Slash Command | User types /cmd | Simple prompt templates | | Hook | Events (tool use, etc) | Automation on actions |

Full comparison: automation-decision-guide.md

Workflow

Step 1: Identify Candidates

If no target specified ("agentify" alone):

Review conversation for automation candidates

Look for: verbose outputs, multi-step workflows, repeated patterns

MUST use multiSelect: true when presenting candidates (users often want multiple)

If target specified: 1. Check local marketplaces first: - ~/.claude/plugins/marketplaces/*/plugins/*/ - Use /skill-dedup command to find overlaps 2. If not found locally, search remote: WebFetch https://claudemarketplaces.com/?search=[keyword] 3. If found, recommend existing or extend. If not, proceed to create

Step 1.5: Merge logic / Grouping / AskUserQuestion

When duplicate or similar automation candidates are found, confirm grouping and merge options with the user using AskUserQuestion.

Grouping criteria:

Similarity in model or functionality

Contextual similarity

Keyword grouping (e.g., "openclaw management")

Merge criteria:

| Condition | Recommendation | | --------- | -------------- | | 3+ similar topics | multi-topic Skill | | Different triggers + same skill | General Agent | | Simple instructions + Bash script | Skill (Agent with skill) | | Complex multi-step + multiple tools | Agent |

AskUserQuestion (merge options): "Candidates found. How should I structure them?" options: - "Merge related topics into one multi-topic skill (e.g., openclaw: exec/gateway/test)" - "Create separate agents for each functionality" - "Skill + Agent combination (instruction=skill, implementation=agent)"

PROHIBITED: Do not create separate agents without merging candidates into a logical structure if they are related.

Step 2: Gather Requirements

Use AskUserQuestion to clarify:

Triggers: Commands or conditions that activate the automation

Tools: Required tools or skills

Scope: Global (~/.claude/) / Project (.claude/)

Language: code comments, variable names, documentation

Question patterns: askuserquestion-patterns.md

Step 3: Recommend Type

Use the automation-decision-guide.md to recommend the best type.

Step 4: Create

CRITICAL: Follow the creation method for each type

Skill with scripts (If scripts are required, use skill directory structure):

skill-name/
├── SKILL.md          # frontmatter + documentation + node scripts/xxx.js (mode)
├── topic-a.md        # topic file
├── topic-b.md        # topic file
└── scripts/
    └── xxx.js        # actual logic (temp location, permanent storage)

Do not create tmp_*.js in current directory; move to scripts/

Call in SKILL.md: node /scripts/xxx.js

Use relative path from __dirname in scripts

Separate implementation logic and topic files

Skill (no scripts): MUST use skill-writer (do NOT create directly)

Skill tool: skill: "project-automation:skill-writer"

Agent: Create in ~/.claude/agents/ or .claude/agents/

agent-templates.md

Rules: Create in ~/.claude/rules/ or .claude/rules/

rules-guide.md

Slash Command: Create in ~/.claude/commands/ or .claude/commands/

slash-command-syntax.md

Hook: Add to settings.json

hook-examples.md

Plugin (open source):

plugin-creation.md

Step 5: Validate

1. Register or copy to target location 2. Reload Claude Code: 1. Manual sync to cache, OR 2. New session to reload

Auto-sync hook: plugin-cache-sync.sh syncs marketplace to cache on Edit/Write

Output Guidelines

Keep responses concise: 1. List identified candidates (with multiSelect) 2. Summarize the recommended structure (Merge logic) 3. Provide the creation plan

| Context | multiSelect | | ------- | ----------- | | Automation candidates | true (users often want multiple) | | Merge options (Complexity) | false (merge vs separation - mutually exclusive) | | Type selection | false (mutually exclusive) | | Scope selection | false (one location) | | Feature selection | true (additive choices) |

Success Case

Scenario (2026-03-09):

Found 3 openclaw-related functions

Proposed 3 options for merging

Result: Implementation success, user satisfied

Key factors: 1. Identification of 3 functions 2. "Merge?" AskUserQuestion 3. merging skills using skill-writer (multi-topic)

Ralph Mode (AskUserQuestion bypass)

If .ralph/ directory exists, operate in Ralph Mode.

Workflow Change:

| Step | User Interaction | Workflow | | ---- | ---------------- | -------- | | Step 1: Auto-detect | AskUserQuestion (multiSelect) | Summary info to .ralph/improvements.md | | Step 1.5: Merge logic / Structure | - | improvements.md recording | | Step 2: Requirements | AskUserQuestion | trigger/scope recommendation to improvements.md | | Step 3: Type recommendation | Recommend only | improvements.md recording | | Step 4: Implementation | Direct action | PROHIBITED - Use [NEEDS_REVIEW] tag | | Step 5: Validation | Validation | Auto validation (after changes are complete) |

improvements.md recording example

## Agentify Candidate (Implementation)
[Candidate Name]
Context: [Why it was found]
Recommended Type: [Skill/Agent/Hook/Slash Command]
Recommended Structure: [Topics]
Rationale: [Why it's recommended]
Tag: [NEEDS_REVIEW]

Self-Improvement

After changes are complete, Self-improve based on conversation:

1. Identify failure and workaround patterns 2. If candidates found, run /skill-kit upgrade agentify