agentleFS
eddieozeddieoz/skills/AGENTS.md

skills

AGENTS.md1 starsChanged 15 days agoMITView on GitHub

Instructions for AI agents to install, configure, and use the writing-assistant skills programmatically. The repository root is a valid Hermes Agent plugin pack. Install the whole collection at once: or paste https://github.com/eddieoz/skills into the desktop "Install from Git" dialog. Individual skills remain available under skills/<name> (and the legacy writing-assistant/<name> path). The repository ships a Claude Code plugin manifest at .claude-plugin/plugin.json (and claude-plugin.json at the root). Install the whole collection with: Skills under skills/ are discovered automatically. Individual skills remain available…

  • Installs packages
  • 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,774 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 repositoryOne other file it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

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

    Add to your profile's config.yaml:

    line 64
  2. Very specific:

    After installation, verify skills are loadable:

    line 93
  3. Distinctive:

    Key constraint: Do NOT be polite. Be precise.

    line 152
  4. Distinctive:

    After installation, verify each skill:

    line 322

≈ “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 — Writing Assistant Skills

Instructions for AI agents to install, configure, and use the writing-assistant skills programmatically.

Repository Structure

# Repo root is now also a Hermes Agent plugin pack:
#   plugin.json   (Agent Plugins v1 manifest)
#   SKILL.md      (meta-skill index)
#   skills/       (symlinks to writing-assistant/*)

writing-assistant/
    ├── critique-content/
    │   ├── SKILL.md
    │   ├── scripts/
    │   │   └── critique_dispatch.py
    │   └── references/
    │       └── red-team-patterns.md
    ├── document-reference-validator/
    │   ├── SKILL.md
    │   ├── scripts/
    │   │   ├── __init__.py
    │   │   ├── check_authority.py
    │   │   ├── extract_references.py
    │   │   ├── fetch_content.py
    │   │   ├── validate_document.py
    │   │   ├── validate_parallel.py
    │   │   └── verify_claim.py
    │   └── references/
    │       └── authoritative-sources.md
    ├── persuasive-analysis/
    │   └── SKILL.md
    ├── proof-read/
    │   └── SKILL.md
    └── text-assessment/
        └── SKILL.md

Installation

Via Hermes Plugin Install (pack)

The repository root is a valid Hermes Agent plugin pack. Install the whole collection at once:

hermes plugins install https://github.com/eddieoz/skills

or paste https://github.com/eddieoz/skills into the desktop "Install from Git" dialog. Individual skills remain available under skills/<name> (and the legacy writing-assistant/<name> path).

Via Claude Code (pack)

The repository ships a Claude Code plugin manifest at .claude-plugin/plugin.json (and claude-plugin.json at the root). Install the whole collection with:

claude plugin install https://github.com/eddieoz/skills

Skills under skills/ are discovered automatically. Individual skills remain available under skills/<name>.

Via Hermes Agent Config

Add to your profile's config.yaml:

skills:
  - name: critique-content
    source: file:///absolute/path/to/skills/writing-assistant/critique-content
  - name: document-reference-validator
    source: file:///absolute/path/to/skills/writing-assistant/document-reference-validator
  - name: persuasive-analysis
    source: file:///absolute/path/to/skills/writing-assistant/persuasive-analysis
  - name: proof-read
    source: file:///absolute/path/to/skills/writing-assistant/proof-read
  - name: text-assessment
    source: file:///absolute/path/to/skills/writing-assistant/text-assessment

Via Symlink (Recommended for Development)

# From your Hermes profile directory
PROFILE_SKILLS=~/.hermes/profiles/cadmus/skills
mkdir -p "$PROFILE_SKILLS"
for skill in critique-content document-reference-validator persuasive-analysis proof-read text-assessment; do
  ln -sfn /absolute/path/to/skills/writing-assistant/$skill "$PROFILE_SKILLS/$skill"
done

Verification

After installation, verify skills are loadable:

# In Hermes session
skill_view(name="critique-content")
skill_view(name="document-reference-validator")
skill_view(name="persuasive-analysis")
skill_view(name="proof-read")
skill_view(name="text-assessment")

Each should return the skill's full SKILL.md content.

Runtime Dependencies

SkillRequires
critique-contentsequential-thinking MCP server, sub-agent delegation (delegate_task), web search
document-reference-validatorPython 3.10+, requests, beautifulsoup4, lxml (see scripts/requirements.txt if present)
persuasive-analysisNone (pure reasoning)
proof-readNone (pure reasoning)
text-assessmentNone (pure reasoning)

Install Python deps for document-reference-validator:

cd /path/to/skills/writing-assistant/document-reference-validator/scripts
pip install -r requirements.txt  # if exists, else:
pip install requests beautifulsoup4 lxml

Agent Usage Patterns

1. critique-content — Hostile Red-Team Analysis

Trigger phrases: "critique this", "red-team", "hostile review", "find flaws", "tear this apart"

Agent workflow:

# 1. Load skill
skill_view(name="critique-content")

# 2. Plan with sequential-thinking (MCP)
#    - Analyze text structure
#    - Determine sectioning strategy
#    - Plan critique dimensions per section
#    - Define fact-checking targets

# 3. Dispatch parallel sub-agents via delegate_task
#    One sub-agent per section with the Hostile Critic prompt

# 4. Synthesize with sequential-thinking
#    - Aggregate findings
#    - Identify cross-cutting patterns
#    - Assess structural integrity

# 5. Deliver red-team report format

Key constraint: Do NOT be polite. Be precise. Fact-check via web search.

2. document-reference-validator — Citation Verification

Trigger phrases: "validate references", "check citations", "verify sources", "fact-check links"

Agent workflow:

# 1. Load skill
skill_view(name="document-reference-validator")

# 2. Choose mode:
#    - Few refs (<5): python scripts/validate_document.py doc.md
#    - Many refs (5+): python scripts/validate_parallel.py doc.md --max-workers 10

# 3. Parse output:
#    - validation-report.md (human-readable)
#    - validation-log.json (machine-readable)
#    - failed-fetches.log (problematic URLs)

# 4. Report statuses: ✅ Verified, ⚠️ Partial, ❌ Mismatch, 🔍 Failed, 🚫 Unreliable, 💥 Error

Key flags:

  • --check-authority — validate source reliability
  • --semantic-threshold 0.5 — stricter matching (default 0.35)
  • --use-browser — force browser automation for JS-heavy sites

3. persuasive-analysis — Rhetorical Diagnosis

Trigger phrases: "analyze persuasion", "rhetorical analysis", "why isn't this convincing", "logos ethos pathos"

Agent workflow:

# 1. Load skill
skill_view(name="persuasive-analysis")

# 2. Identify: Goal + Audience + Context

# 3. Analyze three modes:
#    Logos: claim clarity, evidence quality, reasoning validity, counter-args addressed
#    Ethos: credentials, transparency, fairness, consistency, tone
#    Pathos: emotional hooks, values alignment, vivid language, empathy, ethics

# 4. Evaluate structure: opening, flow, pacing, closing

# 5. Deliver: Rating + Mode breakdown + Top 3 strengths/weaknesses + Prioritized recommendations

Do NOT use for: Pure info text (use text-assessment), creative writing, fact-checking.

4. proof-read — Final Polish

Trigger phrases: "proofread", "polish", "humanize", "fix AI tone", "final pass"

Agent workflow:

# 1. Load skill
skill_view(name="proof-read")

# 2. Three-pass system:
#    Pass 1 - Mechanical: spelling, grammar, punctuation, facts, consistency
#    Pass 2 - Editorial: wordiness, repetition, complex sentences, weak openings, jargon, passive voice
#    Pass 3 - Humanization: remove AI markers (hedging, generic intensifiers, abstract opens, etc.)

# 3. Deliver:
#    - Edited text (ready to use)
#    - Summary: word count delta, mechanical fixes, editorial changes, humanization fixes, flow improvements

Red flags to stop on: word count increased, main point lost, sounds like different person, can't read aloud smoothly.

5. text-assessment — Systematic Evaluation

Trigger phrases: "assess this", "review draft", "evaluate writing", "feedback on this text"

Agent workflow:

# 1. Load skill
skill_view(name="text-assessment")

# 2. Read for understanding (identify core message)

# 3. Evaluate 5 dimensions:
#    Clarity, Logic, Factual Accuracy, Communication, Completeness

# 4. Identify priority issues (macro before micro)

# 5. Deliver report:
#    - Executive summary + single most important improvement
#    - Dimension scores (Excellent/Good/Fair/Poor + justification)
#    - Priority improvements (3-5, ranked High/Medium/Low with "because")
#    - Quick wins (2-3 immediate low-effort fixes)

Do NOT use for: Proofreading only, specialized domain review, style guide enforcement.

Composite Workflows (Agent-Orchestrated)

Pre-Publication Pipeline

# For articles, essays, blog posts before publish
async def pre_publication_review(document_path: str):
    # 1. Structural + completeness check
    assessment = await run_skill("text-assessment", document_path)
    if assessment.overall in ["needs work", "major revision"]:
        return assessment  # Stop early
    
    # 2. Red-team critique
    critique = await run_skill("critique-content", document_path)
    if critique.fatal_flaws > 0:
        return critique  # Stop early
    
    # 3. Citation validation (if references present)
    if has_references(document_path):
        validation = await run_skill("document-reference-validator", document_path, parallel=True)
        if validation.mismatch_or_failed > 0:
            return validation
    
    # 4. Persuasive check (if persuasive intent)
    if is_persuasive(document_path):
        persuasive = await run_skill("persuasive-analysis", document_path)
        if persuasive.rating in ["Weakly Persuasive", "Not Persuasive"]:
            return persuasive
    
    # 5. Final polish
    return await run_skill("proof-read", document_path)

Fact-Check Heavy

# For research-heavy content
async def fact_check_pipeline(document_path: str):
    validation = await run_skill("document-reference-validator", document_path, 
                                  parallel=True, check_authority=True)
    critique = await run_skill("critique-content", document_path)  # focuses on factual claims
    return {"validation": validation, "critique": critique}

Polish Only

# For near-final drafts
async def polish_only(document_path: str):
    assessment = await run_skill("text-assessment", document_path, quick=True)
    if assessment.quick_wins:
        return await run_skill("proof-read", document_path)
    return assessment

Skill Invocation Reference

SkillPrimary Entry PointOutput Format
critique-contentSequential-thinking + delegate_taskRed-team report (markdown)
document-reference-validatorpython scripts/validate_parallel.pyvalidation-report.md, validation-log.json
persuasive-analysisReasoning + structured analysisRating + mode breakdown + recommendations
proof-readThree-pass editingEdited text + change summary
text-assessment5-dimension evaluationExecutive summary + scores + prioritized fixes

Error Handling

Failure ModeRecovery
critique-content sub-agent timeoutReduce section count; increase timeout
document-reference-validator fetch failuresCheck failed-fetches.log; retry with --use-browser
sequential-thinking unavailableFall back to single-pass analysis (note in output)
Python script import errorsVerify venv + dependencies in scripts/

Testing Checklist

After installation, verify each skill:

  • skill_view(name="critique-content") returns content
  • skill_view(name="document-reference-validator") returns content
  • python scripts/validate_parallel.py --help works
  • skill_view(name="persuasive-analysis") returns content
  • skill_view(name="proof-read") returns content
  • skill_view(name="text-assessment") returns content

Versioning

Skills are versioned by their directory timestamp. No semantic versioning — pull latest from source to update.

Support

Issues: Check individual skill SKILL.md for "Common Mistakes" and "Red Flags" sections. For Hermes integration issues, consult Hermes Agent documentation.

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.