skill evolver

Data Community

Skill notes

Trace Format

Traces are JSON with this structure:

Workflow

This skill can receive two types of input (at least one required): Traces: Execution trace data from real skill runs — provides data-driven problem discovery Feedback: User-written improvement suggestions — provides directed guidance for changes When both are provided, combine insights: use traces to validate/discover issues and feedback to prioritize and guide fixes.

Step 1: Analyze Inputs

If traces are provided, run the analysis script: Output includes: Success rate Average turns, duration, tokens Common issues and warnings

Step 2: Extract Issue Details

For failed or problematic traces, extract full context: Skip this step if only feedback was provided (no traces).

Step 3: Identify Root Causes

Map issues to skill components using references/issue-patterns.md: Issue Type · Likely Fix Location execution_failure · scripts/, error handling high_turn_count · SKILL.md clarity, add examples tool_errors · scripts/, input validation

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
@dp-archive · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · GitHub
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

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

01
Step 1: Analyze Inputs

If traces are provided, run the analysis script: Output includes: Success rate Average turns, duration, tokens Common issues and warnings

02
Step 2: Extract Issue Details

For failed or problematic traces, extract full context: Skip this step if only feedback was provided (no traces).

03
Step 3: Identify Root Causes

Map issues to skill components using references/issue-patterns.md: Issue Type · Likely Fix Location execution_failure · scripts/, error handling high_turn_count · SKILL.md clarity, add examples tool_errors · scripts/, input validation

04
Step 4: Apply Fixes

Read the target skill and apply changes based on analysis: For script errors: Fix scripts, add validation, improve error messages For efficiency issues: Add examples, decision trees, clearer instructions For token issues: Reduce SKILL.md, move content to references/ For trigger issues: Update frontmatter description

Discussion

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