agentleFS
ozgurkarahanozgurkarahan/ai-agent-memory/.claude/skills/lint/SKILL.md

lint

Skill8 starsChanged 4 months agoMITView on GitHub

Run wiki health checks (structural + semantic) and report findings by severity: critical (orphans, missing frontmatter), important (cross-reference gaps, thin pages), informational. Trigger: 'lint', 'health check', 'check wiki'.

82 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use coverage, save and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 4 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 5 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 4 projects that use this

  • AnthropicSkill

    digest

    Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.

    Also in 3 projects that use this

  • AWSSkill

    issue

    Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.

    Also in 4 projects that use this

  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user says "lint", "health check", or "check wiki", inspect the wiki directly with the agent's file listing, search, and read tools.

    line 8
  2. Distinctive:

    Before reading or writing:

    line 12
  3. Very specific:

    If memory/schema.md exists in the current workspace, set WIKI_ROOT to memory/.

    line 14
  4. Very specific:

    If none resolves to a folder containing both schema.md and index.md, report the missing path and stop.

    line 17
  5. Very specific:

    All paths below are relative to WIKI_ROOT.

    line 19
  6. Very specific:

    Read schema.md and index.md.

    line 23
  7. Distinctive:

    Run the checks below using the agent's native search/read capabilities:

    line 26
  8. Distinctive:

    Do not modify files unless the user asks for fixes.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “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

Lint Wiki — Agent-Native Health Check

When the user says "lint", "health check", or "check wiki", inspect the wiki directly with the agent's file listing, search, and read tools. This skill has no helper-script dependency.

Resolve the memory root

Before reading or writing:

  1. If memory/schema.md exists in the current workspace, set WIKI_ROOT to memory/.
  2. Else if schema.md exists in the current workspace, set WIKI_ROOT to the current directory.
  3. Else follow the memory-wiki path declared in the current project's AGENT.md.
  4. If none resolves to a folder containing both schema.md and index.md, report the missing path and stop. Do not guess.

All paths below are relative to WIKI_ROOT.

Procedure

  1. Read schema.md and index.md.
  2. Inventory all Markdown pages recursively under wiki/. Treat _index.md files as indexes, not content pages.
  3. Build a slug map from content-page filenames and extract every [[wikilink]] target, ignoring aliases (|...) and headings (#...).
  4. Run the checks below using the agent's native search/read capabilities:

Critical

  • Missing or malformed frontmatter — page does not start with a complete --- block or lacks title, category, date_created, or date_updated.
  • Broken wikilink — target slug does not resolve to a content page.
  • Orphan page — content page has no incoming wikilink from another page or index.
  • Invalid source reference — a source_docs: entry is non-empty but does not resolve to a file under raw/.

Important

  • Missing catalog entry — content page is absent from index.md.
  • Missing category index entry — when wiki/{category}/_index.md exists, it does not link the page.
  • Thin page — fewer than 50 prose words outside frontmatter and headings.
  • Cross-reference gap — two clearly related existing pages mention the same canonical entity but do not link to each other.

Informational

  • Duplicate or ambiguous slugs across category folders.
  • Stale pages whose date_updated is more than six months old.
  • Unlinked glossary terms that appear repeatedly in content.
  1. Present findings by severity with counts, affected paths, and a specific fix for every critical or important issue.
  2. Do not modify files unless the user asks for fixes. If fixes are requested, apply them and rerun this full procedure.
  3. For an ingest gate, compare before/after findings and require zero new issues introduced by that ingest. Pre-existing unrelated findings may remain documented.

Output

## Wiki Health

| Severity | Count |
|---|---:|
| Critical | N |
| Important | N |
| Informational | N |

### Findings
| Severity | Path | Finding | Fix |
|---|---|---|---|

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.