skill evolve

Data Community

Skill notes

When to Use

User invokes this skill after completing work that revealed a gap, pitfall, or new pattern not yet captured in an existing SKILL.md. Typical trigger: /skill-evolve @path/to/SKILL.md

Step 1 — Gather Context

Read the referenced SKILL.md in full. Review the current conversation to identify: What went wrong or was discovered (the incident/finding) Root cause (why it happened) The fix or pattern (what the correct approach is)

Step 2 — Classify the Learning

Determine which type of update is needed: Type · Description · Example New Rule · A pattern/anti-pattern not covered at all · .entered() in async is forbidden Rule Refinement · Existing rule needs caveats or edge cases · skip_all needed when params include trait objects New Example · Correct/incorrect code pattern to illustrate existing rule · async {}.instrument(span).await for match arms

Step 3 — Draft the Update

Write the proposed additions following these principles: Match the existing style — same heading levels, table formats, code block conventions Place it where it belongs — near related content, not appended randomly at the end Lead with the rule, then the why, then the example Include both CORRECT and FORBIDDEN patterns when adding anti-patterns

Step 4 — Apply and Summarize

Edit the SKILL.md with the new content. Present a summary to the user:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
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
@UniClipboard · 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 — Gather Context

Read the referenced SKILL.md in full. Review the current conversation to identify: What went wrong or was discovered (the incident/finding) Root cause (why it happened) The fix or pattern (what the correct approach is)

02
Step 2 — Classify the Learning

Determine which type of update is needed: Type · Description · Example New Rule · A pattern/anti-pattern not covered at all · `.entered()` in async is forbidden Rule Refinement · Existing rule needs caveats or edge cases · `skip_all` needed when params include trait objects New Example · Correct/incorrect code pattern to illustrate existing rule · `async {}.instrument(span).await` for match arms

03
Step 3 — Draft the Update

Write the proposed additions following these principles: Match the existing style — same heading levels, table formats, code block conventions Place it where it belongs — near related content, not appended randomly at the end Lead with the rule, then the why, then the example Include both CORRECT and FORBIDDEN patterns when adding anti-patterns

04
Step 4 — Apply and Summarize

Edit the SKILL.md with the new content. Present a summary to the user:

Discussion

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