capture-feedback
Skill12 starsChanged 18 days agoMITView on GitHub
Turn something heard in the field into durable context, at the right confidence level. Use when the user relays an objection, a competitor mention, a win or loss reason, a signal, or any claim from a call, and asks to remember it. Enforces the repetition rule and the confidence ladder.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- link7373/agentic-pmotheir own version, first seen Aug 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- link7373/agentic-pmo★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/manifest-guardrails.mdcCursor rule
- llms.txtllms.txt
- cadenceSkill
- context-hygieneSkill
- new-executionSkill
- new-motionSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
The confidence ladder: Every file in proof/, signal/, and insight/ carries confidence::
- Distinctive: line 48
Never overwrite a major claim silently: If you are rewriting an existing position, archive the prior version rather than deleting it.
- Very specific: line 51
Lint: Run npm run lint:context. Then report what you wrote and at what confidence.
- Very specific: line 56
Do not invent evidence to justify an upgrade.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Capture feedback into context
The context layer is only worth what its weakest claim is worth. This skill is the gate.
The two rules this enforces
- Repetition. A claim enters
context/after it shows up twice, independently. Once is an anecdote and belongs incadence/log/orcontext/insight/atconfidence: hypothesis. - The confidence ladder. Every file in
proof/,signal/, andinsight/carriesconfidence::hypothesis: we think so. Readable, but outreach plays may not cite it. The linter blocks that.validated: seen at least twice, independently, in the real world.proven: measured and repeatable, with the number to show.
Steps
- Classify what you heard. Which domain does it belong in?
- A pushback in a sales conversation →
objection/ - A number, quote, or customer result →
proof/ - A buying trigger →
signal/ - A market observation that fits nowhere else →
insight/ - A competitor or status-quo alternative →
alternative/ - A won or lost deal and why →
client/
- A pushback in a sales conversation →
- Search for prior occurrences. Grep
context/, recentcadence/log/entries, andoutputs/. Has this shown up before? - Decide the confidence level, honestly.
- Second independent occurrence, no numbers → create or upgrade to
validated, and cite both occurrences in the body. - You have a measured, repeatable number →
proven. - First occurrence → either log it (preferred) or write it at
hypothesis. Say out loud that it is not yet citable by outreach.
- Second independent occurrence, no numbers → create or upgrade to
- Write it. New file from the domain's
_template.md, or upgrade the existing file'sconfidence:and add the new evidence. Cross-reference related files with[[domain/slug]]wikilinks so the knowledge graph connects. - Never overwrite a major claim silently. If you are rewriting an existing position, archive the prior version rather than deleting it.
- Lint. Run
npm run lint:context. Then report what you wrote and at what confidence.
Rules
- Do not invent evidence to justify an upgrade. An honest
hypothesisbeats a fabricatedvalidated. - Upgrading a claim to
validatedunlocks it for outreach copy. Treat that as the consequential act it is.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

