More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    CLAUDE.md Writer

    1

    Write, audit and fix CLAUDE.md, AGENTS.md and .claude/rules from facts in your repository, with a linter that checks them against the code.

    Free

    1 useSecurity scanned
    CLAUDE.md Writer

    CLAUDE.md Writer

    Example session with this skill installed

    Our CLAUDE.md is a year old and Claude keeps running commands that don't exist. Fix it.

    • Read your context and instructions
    • Compiled the claude md writer

    CLAUDE.md audited and rewritten

    I ran the linter against the repo first

    $ python lint_claude_md.py
    WARN  CLAUDE.md:1   [shouting] 6 uses of IMPORTANT/MUST/NEVER/ALWAYS in caps
    ERROR CLAUDE.md:6   [commands] `pnpm run e2e`: no package.json script named 'e2e'
    ERROR CLAUDE.md:7   [commands] `make deploy`: there is no Makefile
    WARN  CLAUDE.md:10  [paths] `src/checkout/` does not exist in the repo
    WARN  CLAUDE.md:13  [vague] "write clean code" cannot be verified
    WARN  CLAUDE.md:14  [conflicts] says both use and do not use 'moment'
    ERROR CLAUDE.md:16  [secrets] looks like a connection string with password
    
    3 error, 4 warning, 0 info
    

    What I changed

    ProblemFix
    pnpm run e2e and make deploy do not existReplaced with the commands CI runs: pnpm test, pnpm lint, pnpm typecheck
    src/checkout/ was removed in a refactorRemoved; the file now names src/orders/ and src/payments/
    "Never use moment" and "use moment for timezones"Kept one rule: dates are ISO 8601 in UTC at the API
    A staging database URL with passwordRemoved; it now names DATABASE_URL. Rotate that password, it has been in git
    Six rules in capitalsPlain, specific instructions

    Added what was missing: how to run one test (pnpm vitest run src/orders/service.test.ts) and a "before saying a task is done" line.

    $ python lint_claude_md.py
    Checked CLAUDE.md (16 lines)
    0 error, 0 warning, 0 info
    

    Next step

    Add python lint_claude_md.py to CI so the file fails the build when it drifts from the code again.

    CLAUDE.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    What it does

    The instruction file is read at the start of every agent session. Most are generated once and never checked, or grow into generic advice the agent stops following. This skill writes one from verified facts and keeps it honest.

    Two scripts, standard library only

    repo_facts.py reports what the repo actually contains: every defined command (package.json per workspace, Makefile, justfile, Taskfile, pyproject, tox, nox, composer), what CI really runs, toolchain and versions, lint/test/type tools, layout, existing agent files for Claude, Codex, Cursor, Copilot, Gemini and Windsurf, commit style, and env var names (never values).

    lint_claude_md.py checks the instruction file against the repo:

    • commands that do not exist (pnpm run e2e, make deploy), with dependency binaries like pnpm vitest understood
    • paths that moved, broken or too-deep @imports
    • secrets, vague rules nobody can verify, contradictions, too much shouting
    • oversized files, rules frontmatter that silently fails, an AGENTS.md Claude Code ignores, a CLAUDE.local.md about to be committed
    • non-zero exit on errors, so it runs in CI and pre-commit

    The workflow

    Collect facts, verify the commands, ask only what files cannot answer (at most five questions), write under 200 lines, put area-specific rules in path-scoped .claude/rules/, lint until clean. Includes a writing guide with before/after examples, a template, and a complete example file.

    Tested on real repositories (a Python library and a large pnpm monorepo) and with 19 automated tests.

    Built by Nex AI, nex-ai.be

    The linter verifies npm, pnpm, yarn and bun scripts, make and just targets; other command runners are not checked. Path checks cover paths written in backticks. It checks facts, it cannot judge whether a rule is wise.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    • Free with an Agensi account

    Requires

    Python 3.8+
    vitest
    Node.js
    jest
    Python
    downloads
    prettier
    @biomejs/biome
    cowsay
    tools

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Terminal to run the two scripts and git (commit style). Read files to collect repository facts and lint the instruction files. Write files to create or update CLAUDE.md, AGENTS.md and .claude/rules. No network.

    Listed29 days ago

    What's inside

    Frequently Asked Questions

    /init drafts a file once. This skill grounds every command in the repo or CI, asks only what files cannot answer, places area-specific rules where they load on demand, and the linter keeps the file true as the code changes.

    Yes. The linter checks AGENTS.md and rules files, and warns when Claude Code would silently ignore an AGENTS.md next to a CLAUDE.md.

    No. It shows a diff with a reason for every removed section and never drops your content silently.

    New in Prompt & Skill Engineering