agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/strength-assessment/SKILL.md

strength-assessment

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Tactic for assessing argument strength — evaluate evidence quality, count independent sources, check for defeaters, assign calibrated confidence scores.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Must score ≥3 claims per invocation.

    line 15

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

Strength Assessment

Evaluate the strength of claims based on their evidential support.

Minimum Yield

<HARD-GATE> Must score ≥3 claims per invocation. </HARD-GATE>

Protocol

  1. For each claim, gather all linked evidence (supporting and contradicting)
  2. Evaluate evidence quality:
    • Source reliability (peer-reviewed > preprint > blog)
    • Directness (direct test > indirect inference > analogy)
    • Independence (multiple independent sources > single source chain)
  3. Check for defeaters:
    • Undercutting defeaters (evidence that the support doesn't actually support)
    • Rebutting defeaters (evidence directly contradicting the claim)
    • Undermining defeaters (evidence that the evidence itself is unreliable)
  4. Assign strength score (0-10) with explicit reasoning via strength-scoring
  5. Flag claims with score < 3 as "weak" and claims with score > 7 as "strong"

SOPs Used

  • strength-scoring — assign and record strength scores
  • evidence-attachment — create additional evidence links discovered during assessment

Yield Report

Returns: { claims_scored: number, strong_claims: number, weak_claims: number, defeaters_found: number }

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.

Check your setup, free