analyze
Skill1 starsChanged 5 months agoMITView on GitHub
Evidence-based deep analysis of one repo — onboards a stub into a real note, or verifies and corrects a drifted note. The only place milestone boxes get checked, always with citations. Use to onboard a repo, after a stale-thread warning, or when a note seems wrong.
73 other projects use a version of this.
Adopted by
Most recently taken up by
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- link7373/agentic-bi-teamtheir own version, first seen Nov 10, 2026
- ansvisor/ansvisortheir own version, first seen Nov 8, 2026
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tooltheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use constitution, revise and 10 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.
ArvorCoSkillconstitution
Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.
Also in 4 projects that use this
stormlightlabsSkillrevise
Address review comments on an open pull request and push the fixes. Use for /edit, /revise, or when asked to respond to review feedback on a PR number.
Also in 3 projects that use this
DockerSkillwrite
Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.
Also in 6 projects that use this
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 5 projects that use this
H-mmerSkillsubmit
Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.
Also in 3 projects that use this
GoogleSkillquality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
Also in 3 projects that use this
- +1 more from ArvorCo
Other versions73 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 73
- anthropics/knowledge-work-plugins★ 36ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- oxsecurity/megalinter★ 2.6ksame name
- H-mmer/pentest-agents★ 815same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- hardisgroupcom/sfdx-hardis★ 432same name
- nwiizo/tfmcp★ 373same name
- hsantanna88/clo-author★ 262same name
- hugosantanna/clo-author★ 262same name
- ansvisor/ansvisor★ 241same name
63 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- end-sessionSkill
- setupSkill
- start-sessionSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 63 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 26
Every mark cites evidence inline.
“Common” is measured: kept by at least 6 in 10 of the 63 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.
Files
second-brain: analyze
The evidence engine. Follow the discipline below EXACTLY — Part 2 governs this skill.
!cat "${CLAUDE_PLUGIN_ROOT}/references/discipline.md"
Steps
- Locate the vault (cwd or ancestors containing
Projects/Dashboard.md; else registered vaults in~/.claude/second-brain/vaults, ask if several; none → "run /second-brain:setup first"). Resolve the repo: the argument, else cwd, else ask. Locate its note in<vault>/Projects/by frontmatterrepo:match; missing → create fromProjects/_TEMPLATE.md; auto-stub → this is an onboarding run. - Read the evidence, in Part 2 order: README/docs → manifest → source tree → tests (run them only if cheap and safe — a test suite, not a deploy) →
git -C <repo> log --oneline -30→ open PRs/issues viaghif available. - Write the note:
## 📌 One-linerfrom what the code actually is.## 🏁 Milestoneswith cited marks per Part 2 ([x]artifact+tests/commit ·[~]partial, cite present AND missing ·[ ] needs check).- Claims-vs-evidence contradictions recorded explicitly (e.g. "README claims billing ready;
src/billing/stripe.tsis a stub with 0 tests → [~]"). - frontmatter
status+last_updated. Do NOT touch## ▶ Threadorlast_handoff_commit.
- Resolve TODO verification tasks left by end-session (
confirm milestone "…"): verify each against evidence, mark the milestone accordingly with its citation, remove the TODO line. - Update the Dashboard row: Status · Updated (fill Last session/Next only if the columns are empty — they belong to end-session).
- Report: what the evidence showed, every correction made, contradictions found — and invite the user to correct anything inferred.
Rules
- Every mark cites evidence inline. No percentages. Code beats docs. Unknown → needs check. Never write to
## ▶ Thread.
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.

