skill feedback collection

Other Community

Skill notes

Phase 1 — Automated Signal Collection

Review your own session transcript. No human interaction needed yet.

1a: Skills inventory

Before analyzing gaps and errors, inventory all skills that were available during the session: Loaded and used: Skills you read and actively followed. Available but not loaded: Skills that were installed (discoverable via npx @tanstack/intent@latest list) but you never read. This is important — many issues stem from

1b: Gap detection

Identify moments where the skill was silent and you had to bridge the gap yourself — via code reading, search, trial-and-error, or general knowledge. For each gap, note: What you needed to do What the skill should have told you

1c: Error/correction tracking

Identify moments where the skill prescribed an approach that produced an error. For each error, note: What the skill said to do The error or incorrect behavior that resulted The fix you applied

1d: Human intervention events

Identify moments where the human clarified, corrected, or overrode your approach. For each intervention, note: What you were doing when the human intervened What the human said or changed Whether the skill could have prevented this

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
@TanStack · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
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
Phase 1 — Automated Signal Collection

Review your own session transcript. No human interaction needed yet.

02
Phase 2 — Human Interview

Ask the human up to 4 questions. Keep it brief — skip questions if the session already provided clear answers. Respect if they decline. "Was anything unclear about what was happening during the task?" "Did anything feel frustrating or take longer than expected?" "Were you uncertain about the output quality at any point?"

03
Phase 3 — Build the Feedback

Write one Markdown feedback file per skill used. Only include skills that were actually used during the session — skip any that were loaded but never referenced.

04
Phase 4 — Submit

Determine the target repo from the skill's package. The repo is typically derivable from the `repository` field in the package's `package.json`, or from the `sources` field in the SKILL.md frontmatter.

Discussion

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