agentleFS
OKHP3OKHP3/skillz/.agents/skills/static-route-validation/SKILL.md

static-route-validation

Skill3 starsChanged 2 months agoMITView on GitHub

Check Forge route declarations and hash-anchor targets without requiring a browser dependency.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run after changing App.tsx, FAQ anchors, route components, or static hosting configuration.

    line 10

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

Static route and anchor validation

Use when

Run after changing App.tsx, FAQ anchors, route components, or static hosting configuration. This is a deterministic source check and complements browser testing when a browser runner is available.

Callable command

node .agents/skills/static-route-validation/run.mjs

Inputs and outputs

The command reads artifacts/forge/src/App.tsx and the FAQ data source, checks the expected route/anchor contract, and exits non-zero for a missing route, malformed hash target, or missing focus handling. It does not need private credentials or network access.

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.