systems-check
Skill19 starsChanged 28 days agoLicence not identifiedView on GitHub
對「現在這個專案」做一次 agent 自我體檢：掃規則衝突與重複、疑似未使用、可省 token 的常駐脈絡、log 裡沒人處理的 error、security 疑點；只找問題、寫報告與檔案版交接卡，不改任何被掃的來源。當使用者說「系統自檢」「跑自檢」「agent 自檢」「體檢」「巡檢」「systems-check」「self-check」時觸發。⚠️ 只找不修，絕不代替你改規則或修 bug。 English triggers: "systems check", "self-check", "run a health check on this project", "scan for rule conflicts", "audit this repo".
- Reads credentials
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-reviewSkill
- ai-searchSkill
- daily-debriefSkill
- damage-reportSkill
- dropoffSkill
- flight-to-calendarSkill
- mission-logSkill
- new-missionSkill
- pickupSkill
- save-allSkill
- token-optimizerSkill
- weekly-debriefSkill
The file
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.