agentleFS
ahmadelswifyahmadelswify/agentic-os/.claude/skills/log-outcome/SKILL.md

log-outcome

Skill33 starsChanged 31 days agoMITView on GitHub

Capture the result of an interview or application with learnings

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Update story outcome logs for any stories used

    line 15
  2. Distinctive:

    Update the application tracker

    line 21
  3. Distinctive:

    Always extract at least one learning

    line 26
  4. Distinctive:

    If offer: capture compensation and decision timeline

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Log Outcome

The user has an outcome (offer, rejection, or withdrawal) to capture.

How to Do This

  1. Record the outcome in Applications/[company]/outcome.md
  2. Capture: what worked, what didn't, stage reached
  3. Update story outcome logs for any stories used
  4. Extract learnings to propagate to Learnings/:
    • Communication patterns that worked or failed
    • Domain vocabulary insights
    • Story adjustments needed
    • Items for the never-use list
  5. Update the application tracker

Important

  • Handle rejections constructively
  • Always extract at least one learning
  • Push for specifics: "What feedback did they give?"
  • If offer: capture compensation and decision timeline

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.