skill debrief

Other Community

Skill notes

When to use

Trigger when the user wants to debrief an existing SKILL.md based on what happened in the session. Examples: "debrief the X skill" / "let's debrief X" "retrospective on X" / "feedback on X" "improve the X skill" / "let's update X based on what we learned"

Step 1: Identify the skill

Ask which skill is being improved if it isn't obvious from context. Then locate the source: Two cases — they have different update paths: Case · Source location · Update path In-repo ({path = "./skills/<name>", type = "skill"} in agr.toml) · skills/<name>/ · Edit source → commit → agr upgrade <name>

Step 2: Receive feedback

Listen. The user invoked this skill because they have something to say — let them say it. Do not interrogate. Do not run a checklist of questions at them. Take in whatever they offer, in whatever shape they offer it. Only ask a clarifying question if you genuinely cannot proceed without one (e.g. the user named a skill that doesn't exist, or two skills share the

Step 3: Propose changes

Summarize what you heard, then propose specific edits. Format: Proposed changes to skills/<name>/SKILL.md (and any references): 1. Description — add trigger phrase "…" (because: …) 2. Boundaries — add: never X (because: discovered this in session) 3. New section "Y" — describes the workflow that was missing

Step 4: Apply (in-repo case)

Edit the source file(s) under skills/<name>/. Then: Do not push. Stop after the commit and let the user push when ready.

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
@computerlovetech · no license declared
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: Identify the skill

Ask which skill is being improved if it isn't obvious from context. Then locate the source: Two cases — they have different update paths: Case · Source location · Update path In-repo (`{path = "./skills/<name>", type = "skill"}` in `agr.toml`) · `skills/<name>/` · Edit source → commit → `agr upgrade <name>`

02
Step 2: Receive feedback

Listen. The user invoked this skill because they have something to say — let them say it. Do not interrogate. Do not run a checklist of questions at them. Take in whatever they offer, in whatever shape they offer it. Only ask a clarifying question if you genuinely cannot proceed without one (e.g. the user named a skill that doesn't exist, or two skills share the

03
Step 3: Propose changes

Summarize what you heard, then propose specific edits. Format: Proposed changes to `skills/<name>/SKILL.md` (and any references): 1. Description — add trigger phrase "…" (because: …) 2. Boundaries — add: never X (because: discovered this in session) 3. New section "Y" — describes the workflow that was missing

04
Step 4: Apply (in-repo case)

Edit the source file(s) under `skills/<name>/`. Then: Do not push. Stop after the commit and let the user push when ready.

05
Step 5: Apply (remote case)

If the skill is a remote dep, the change cannot be applied directly. Ask the user which path they want:

06
Step 6: Verify

After re-installing (in-repo case): For remote case (issue filed): confirm the issue URL with the user. Tell the user what's done and what's pending (commit done, push pending; or issue filed, awaiting response).

Discussion

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