agentleFS
getcargohqgetcargohq/cargo-manifest/.agents/skills/capture-feedback/SKILL.md

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

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    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.

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
  1. Very specific:

    The confidence ladder: Every file in proof/, signal/, and insight/ carries confidence::

    line 16
  2. Distinctive:

    Never overwrite a major claim silently: If you are rewriting an existing position, archive the prior version rather than deleting it.

    line 48
  3. Very specific:

    Lint: Run npm run lint:context. Then report what you wrote and at what confidence.

    line 51
  4. Very specific:

    Do not invent evidence to justify an upgrade.

    line 56

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Repetition. A claim enters context/ after it shows up twice, independently. Once is an anecdote and belongs in cadence/log/ or context/insight/ at confidence: hypothesis.
  2. The confidence ladder. Every file in proof/, signal/, and insight/ carries confidence::
    • 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

  1. 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/
  2. Search for prior occurrences. Grep context/, recent cadence/log/ entries, and outputs/. Has this shown up before?
  3. 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.
  4. Write it. New file from the domain's _template.md, or upgrade the existing file's confidence: and add the new evidence. Cross-reference related files with [[domain/slug]] wikilinks so the knowledge graph connects.
  5. Never overwrite a major claim silently. If you are rewriting an existing position, archive the prior version rather than deleting it.
  6. 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 hypothesis beats a fabricated validated.
  • Upgrading a claim to validated unlocks it for outreach copy. Treat that as the consequential act it is.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.