broken-link-check
Skill1 starsChanged 2 months agoNo licenceView on GitHub
broken-link 偵測工具。掃描 .claude/ 目錄所有 Markdown 文件中的路徑引用，偵測失效連結。Use for: (1) 一次性掃描所有 broken links, (2) 搭配 /loop 定期監控, (3) 修改規則/方法論/代理人文件後驗證路徑完整性。Use when: user runs /broken-link-check, 或搭配 /loop 定期執行, 或發現 broken link 錯誤後。
In this repository75 other files it gives its agents.
- 5w1h-decisionSkill
- agent-teamSkill
- asd-ste100Skill
- blank-slate-reviewSkill
- branch-worktree-guardianSkill
- bulk-evaluateSkill
- business-analysisSkill
- business-researchSkill
- case-first-module-workflowSkill
- cc-release-impact-reviewSkill
- chrome-extension-mcp-debugSkill
- cognitive-load-assessmentSkill
- component-contract-designSkill
- compositional-writingSkill
- content-extension-evaluationSkill
- continuous-learningSkill
- dart-comment-traceabilitySkill
- dart-domain-modelingSkill
- dart-provider-architectureSkill
- dart-style-guardianSkill
- dart-test-async-guardianSkill
- data-extractionSkill
- decision-tree-helperSkill
- design-decision-frameworkSkill
- dispatch-strategy-reviewSkill
- doc-flowSkill
- docSkill
- error-patternSkill
- event-flow-arbitration-designSkill
- evidence-driven-bugfixSkill
- foundation-designSkill
- framework-issueSkill
- frontend-with-playwrightSkill
- golden-path-validationSkill
- impeccableSkill
- knowledge-cardsSkill
- linux-install-debugSkill
- lsp-firstSkill
- mermaid-asciiSkill
- methodology-writingSkill
- migration-playbook-methodologySkill
- multi-round-reviewSkill
- multi-session-orchestrationSkill
- neurodivergent-outputSkill
- observability-stackSkill
- parallel-evaluationSkill
- pre-fix-evalSkill
- project-analysisSkill
- project-initSkill
- requirement-protocolSkill
- saas-tech-selectionSkill
- scope-confirmationSkill
- search-tools-guideSkill
- skill-design-guideSkill
- skill-syncSkill
- specSkill
- startup-checkSkill
- strategic-compactSkill
- system-designSkill
- system-misjudgmentSkill
- The first 60 shown.
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.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.