agentleFS
frankxaifrankxai/geninvestor-skills/skills/calibration-log/SKILL.md

calibration-log

Skill0 starsChanged 12 days agoApache-2.0View on GitHub

Keep a dated, append-only record of research criteria and resolve them against primary evidence. Use when reviewing a thesis criterion, checking a past research statement, or recording a sourced resolution.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Keep the log append-only. Corrections supersede an entry.

    line 14
  2. Distinctive:

    Check whether the evidence available at registration supported the statement.

    line 15
  3. Distinctive:

    Use explicit unknown states.

    line 23
  4. Distinctive:

    Never output probabilities, price targets, position sizes or trading advice.

    line 27
  5. Distinctive:

    Never backdate, delete a miss or reinterpret the criterion after resolution.

    line 28
  6. Distinctive:

    Never register a forecast through a tool.

    line 29
  7. Distinctive:

    Do not treat missing evidence as a met criterion.

    line 30

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

Research resolution log

Record what was stated, when it was knowable, and what the primary source later showed. The existing skill name is retained for compatibility.

Workflow

  1. Record a precise research criterion, its registration time, resolution date and primary resolution source. Mark historical imports as retrospective.
  2. Resolve only after the source is available. Use met, not met, or cannot be checked. Preserve the original wording and cite the document and field.
  3. Keep the log append-only. Corrections supersede an entry; they never overwrite it.
  4. Check whether the evidence available at registration supported the statement. Keep later restatements distinct from the originally filed version.
  5. Report source gaps and unresolved criteria. Every displayed figure needs a linked, audited claim.

Output

IDRegisteredCriterionResolves onPrimary sourceResolutionEvidence claim

Use explicit unknown states. Keep advice and generated forecasts out of the log.

Rules

  • Never output probabilities, price targets, position sizes or trading advice.
  • Never backdate, delete a miss or reinterpret the criterion after resolution.
  • Never register a forecast through a tool.
  • Do not treat missing evidence as a met criterion.

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.