skill updater

Engineering Community

Skill notes

When to Use

Use this skill when: User provides feedback about an existing skill's performance User wants to improve or modify a skill User reports issues or bugs with a skill User wants to add new functionality to an existing skill

Required Inputs

Skill Path: Path to the skill directory or .skill file to update Feedback: Description of what needs to change, improve, or be fixed

Step 1: Load and Understand the Skill

Use the analyze_skill.py script to get a quick overview: This shows: Skill name and description SKILL.md line/word count All bundled resources (scripts/, references/, assets/)

Step 2: Analyze the Feedback

Categorize the feedback into one or more types: Type · Example Feedback · Typical Changes Bug fix · "The script fails when..." · Fix scripts, add error handling Missing feature · "It should also support..." · Add new functionality Clarity · "Instructions are confusing" · Improve SKILL.md documentation

Step 3: Plan the Changes

Before making changes, create a clear plan: List specific files to modify Describe what changes each file needs Identify any new files to create or files to delete Consider impact on other parts of the skill

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@dp-archive · Complete terms in LICENSE.txt
Token usage
Lean
Setup complexity
Plug-and-play
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
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: Load and Understand the Skill

Use the analyze_skill.py script to get a quick overview: This shows: Skill name and description SKILL.md line/word count All bundled resources (scripts/, references/, assets/)

02
Step 2: Analyze the Feedback

Categorize the feedback into one or more types: Type · Example Feedback · Typical Changes Bug fix · "The script fails when..." · Fix scripts, add error handling Missing feature · "It should also support..." · Add new functionality Clarity · "Instructions are confusing" · Improve SKILL.md documentation

03
Step 3: Plan the Changes

Before making changes, create a clear plan: List specific files to modify Describe what changes each file needs Identify any new files to create or files to delete Consider impact on other parts of the skill

04
Step 4: Implement Changes

Apply changes following skill design principles: For SKILL.md changes: Keep body under 500 lines Use imperative form Move detailed content to references/ if approaching limit

05
Step 5: Validate and Package

After implementing changes:

Discussion

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