skill improver

AI Community

Skill notes

When to Run

Proactive (run without being asked): A build, deploy, or CI job failed and was debugged A task took more than 3 rounds of trial-and-error A session lasted more than one hour and involved multiple skill uses The user explicitly expressed frustration or surprise at a gap

Step 1 — Reflect

Catalog observations in three buckets, with concrete examples: What went well: Patterns, tools, or decisions that saved time or prevented errors Skill instructions that proved particularly useful Diagnoses or fixes that were reached quickly

Step 2 — Classify

Group findings into three categories. For each finding, identify the concrete artifact that needs to change (file path, skill section, CI workflow, etc.). Skill changes — improvements to an existing skill: Missing failure entries in a diagnosis table Wrong fix instructions

Step 3 — Apply

If no improvements are identified: state that explicitly and stop. Do not invent changes. The user can always override the plan/execute decision. If the user says "just fix it directly" for something that would normally need a plan, apply the changes directly instead. If the user says "make a plan" for something small, create one. For obvious fixes (typos, missing warnings, incomplete instructions):

Step 4 — Verify

After applying fixes (directly or via plan execution): Run format/lint commands if the changed files are in checked languages For scripts, run a syntax check and a quick smoke test Re-read the changed skill sections to ensure they don't contradict other parts of the skill or adjacent skills Summarize what was changed and why

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
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
@fjrevoredo · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
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 — Reflect

Catalog observations in three buckets, with concrete examples: What went well: Patterns, tools, or decisions that saved time or prevented errors Skill instructions that proved particularly useful Diagnoses or fixes that were reached quickly

02
Step 2 — Classify

Group findings into three categories. For each finding, identify the concrete artifact that needs to change (file path, skill section, CI workflow, etc.). Skill changes — improvements to an existing skill: Missing failure entries in a diagnosis table Wrong fix instructions

03
Step 3 — Apply

If no improvements are identified: state that explicitly and stop. Do not invent changes. The user can always override the plan/execute decision. If the user says "just fix it directly" for something that would normally need a plan, apply the changes directly instead. If the user says "make a plan" for something small, create one. For obvious fixes (typos, missing warnings, incomplete instructions):

04
Step 4 — Verify

After applying fixes (directly or via plan execution): Run format/lint commands if the changed files are in checked languages For scripts, run a syntax check and a quick smoke test Re-read the changed skill sections to ensure they don't contradict other parts of the skill or adjacent skills Summarize what was changed and why

Discussion

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