fb

Appends verbatim feedback notes to the correct docs/feedback.md inbox file.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/line7works/tony-skills --skill fb-line7works
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fb
Source: https://github.com/line7works/tony-skills/tree/main/plugins/fb/skills/fb
Command: npx skills add https://github.com/line7works/tony-skills --skill fb-line7works

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mid-thread feedback and observations often get lost because capturing them properly requires deciding where they belong and formatting them consistently. This Skill routes each note to the right feedback inbox and appends it verbatim, with zero analysis or triage. ## Core Features & Use Cases - Routing logic: Loop-skill notes (blueprint/build/signoff/recheck, SKILL NOTE lines) go to the central loop feedback doc; all other notes go to the current repo's docs/feedback.md, resolved fresh via git on every capture. - Verbatim capture: Notes are quoted exactly as given and appended as dated inbox lines, with duplicates logged anyway as signal. - Confirmation with drift guard: Every capture ends with the absolute path written and the current Inbox entry count, so a wrong destination is visible immediately. - Use Case: While reviewing a build slice you notice a friction point — say "fb: the signoff step dropped my context" and the note lands in the loop feedback doc for later batch triage. ## Quick Start Say "fb: the blueprint step asked too many clarifying questions" to log that feedback note to the correct inbox.

Frequently Asked Questions about fb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log feedback during a Claude Code session?

Say "fb" followed by your note, or ask to log or note the feedback. The note is appended verbatim as a dated line to the appropriate docs/feedback.md inbox, and the path plus entry count is confirmed back to you.

Where does captured feedback get saved?

Notes about loop skills (blueprint, build, signoff, recheck) go to ~/Developer/tony-skills/docs/feedback.md. All other notes go to the current repository's docs/feedback.md, with the repo root resolved fresh via git rev-parse on every capture.

Does the fb skill analyze or triage feedback notes?

No, it performs capture only. Notes are quoted verbatim with no analysis, severity ratings, or fixes; triage happens in a separate batch session where a skill like blueprint turns notes into slices.

What happens if the feedback target file does not exist?

For a repo inbox, docs/feedback.md is created on first use with a standard Inbox and Dispositions template. For the loop feedback doc, a missing file stops the capture with a report rather than recreating it.

Can duplicate feedback notes be logged?

Yes, apparent duplicates are logged anyway and flagged in the confirmation, since repeated notes are treated as signal. Lines are never edited, reordered, or deleted from the Inbox.