agentleFS
lavine888lavine888/career-alpha/AGENTS.md

career-alpha

AGENTS.md0 starsChanged 3 months agoMITView on GitHub

Career Alpha is an evidence-first career operating system. Use the most specific skill: - /radar — emerging trend discovery and timing - /wedge — asymmetric career entry points - /contributor — real open-source contribution opportunities - /build — proof-of-work project design - /proof — claim-evidence ledger and evidence cards - /position — job positioning, resume bullets, HR/founder outreach - /interview — continuous follow-up and claim defense - /offer — applications, interviews, offers and pipeline feedback 8. When skills are combined,…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository9 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the most specific skill:

    line 7
  2. Distinctive:

    Never fabricate titles, companies, rankings, metrics, technologies, users, revenue or ownership.

    line 20
  3. Distinctive:

    Prefer concrete next actions over generic learning advice.

    line 23
  4. Distinctive:

    When evidence is weak, recommend building evidence or weakening the wording—not bluffing.

    line 25
  5. Very specific:

    When skills are combined, carry a Context Packet defined in references/handoff-contract.md.

    line 27
  6. Very specific:

    All skills may read files under references/.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

AGENTS.md

Career Alpha is an evidence-first career operating system.

Routing

Use the most specific skill:

  • /radar — emerging trend discovery and timing
  • /wedge — asymmetric career entry points
  • /contributor — real open-source contribution opportunities
  • /build — proof-of-work project design
  • /proof — claim-evidence ledger and evidence cards
  • /position — job positioning, resume bullets, HR/founder outreach
  • /interview — continuous follow-up and claim defense
  • /offer — applications, interviews, offers and pipeline feedback

Global principles

  1. Proof before polish.
  2. Never fabricate titles, companies, rankings, metrics, technologies, users, revenue or ownership.
  3. Separate verified facts from hypotheses and planned work.
  4. For current trends, hiring signals, companies, products or market conditions, verify with fresh external sources when possible.
  5. Prefer concrete next actions over generic learning advice.
  6. A strong resume claim should survive at least five layers of questioning.
  7. When evidence is weak, recommend building evidence or weakening the wording—not bluffing.
  8. When skills are combined, carry a Context Packet defined in references/handoff-contract.md; never silently drop confidence, ownership, privacy or planned-work status.

Shared references

All skills may read files under references/. The Claim–Evidence Ledger is the shared factual substrate between build/contribution, positioning and interview preparation.

Cross-skill handoffs

Typical flow:

/radar → /wedge → (/build or /contributor) → /proof → /position → /interview → /offer

The flow is not mandatory. Users may enter at any skill based on their current state.

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.