skillify

Other Community

Skill notes

Step 1: Analyze the Session

Before asking any questions, analyze the full conversation to identify: What repeatable process was performed What the inputs/parameters were The distinct steps (in order) The success artifacts/criteria (e.g. not just "writing code," but "an open PR with CI fully passing") for each step

Step 2: Interview the User

You will use the AskUserQuestion tool to understand what the user wants to automate. Important notes: Use AskUserQuestion for ALL questions! Never ask questions via plain text. For each round, iterate as much as needed until the user is happy. The user always has a freeform "Other" option to type edits or feedback -- do NOT add your own "Needs tweaking" or "I'll provide edits" option. Just offer the substantive choices.

Step 3: Write the SKILL.md

Create the skill directory and file at the location the user chose in Round 2. Use this format: Per-step annotations: Success criteria is REQUIRED on every step. This helps the model understand what the user expects from their workflow, and when it should have the confidence to move on. Execution: Direct (default), Task agent (straightforward subagents), Teammate (agent with true parallelism and inter-agent communication), or [human] (user does it). Only needs specifying if not Direct.

Step 4: Confirm and Save

Before writing the file, output the complete SKILL.md content as a yaml code block in your response so the user can review it with proper syntax highlighting. Then ask for confirmation using AskUserQuestion with a simple question like "Does this SKILL.md look good to save?" -- do NOT use the body field, keep the question concise. After writing, tell the user: Where the skill was saved How to invoke it: /{{skill-name}} [arguments]

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ZhangHanDong · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Analyze the Session

Before asking any questions, analyze the full conversation to identify: What repeatable process was performed What the inputs/parameters were The distinct steps (in order) The success artifacts/criteria (e.g. not just "writing code," but "an open PR with CI fully passing") for each step

02
Step 2: Interview the User

You will use the AskUserQuestion tool to understand what the user wants to automate. Important notes: Use AskUserQuestion for ALL questions! Never ask questions via plain text. For each round, iterate as much as needed until the user is happy. The user always has a freeform "Other" option to type edits or feedback -- do NOT add your own "Needs tweaking" or "I'll provide edits" option. Just offer the substantive choices.

03
Step 3: Write the SKILL.md

Create the skill directory and file at the location the user chose in Round 2. Use this format: Per-step annotations: Success criteria is REQUIRED on every step. This helps the model understand what the user expects from their workflow, and when it should have the confidence to move on. Execution: `Direct` (default), `Task agent` (straightforward subagents), `Teammate` (agent with true parallelism and inter-agent communication), or `[human]` (user does it). Only needs specifying if not Direct.

04
Step 4: Confirm and Save

Before writing the file, output the complete SKILL.md content as a yaml code block in your response so the user can review it with proper syntax highlighting. Then ask for confirmation using AskUserQuestion with a simple question like "Does this SKILL.md look good to save?" -- do NOT use the body field, keep the question concise. After writing, tell the user: Where the skill was saved How to invoke it: `/{{skill-name}} [arguments]`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.