check
Skill245 starsChanged 9 months agoMITView on GitHub
Verify all outputs exist after creating a new component and fix any issues
- Reads credentials
88 other projects use a version of this.
Adopted by
Most recently taken up by
- beCyborg/jadlis-nupptheir own version, first seen Nov 16, 2026
- kotaroyamazaki/godot-agent-kittheir own version, first seen Nov 16, 2026
- brquatti/readme-styletheir own version, first seen Nov 15, 2026
- congptvinadic-debug/token-diettheir own version, first seen Nov 15, 2026
- aldohushi1-stack/glassboxtheir own version, first seen Nov 15, 2026
- stericishere/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use daily-arxiv, exp-eval 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.
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
JuliusBrusseeSkillbackprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
Also in 4 projects that use this
skyllwtSkillexp-pilot-eval
Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.
Also in 4 projects that use this
skyllwtSkillexp-pilot-run
Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.
Also in 4 projects that use this
- +6 more from Lambenthan
- +1 more from skyllwt
Other versions88 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 88
- tw93/Waza★ 7.6ksame name
- tw93/claude-health★ 7.5ksame name
- katanemo/archgw★ 7.1ksame name
- katanemo/plano★ 7.1ksame name
- tokio-rs/topcoat★ 6.4ksame name
- Giskard-AI/giskard-oss★ 6ksame name
- VibiumDev/vibium★ 3ksame name
- skyllwt/OmegaWiki★ 1.7ksame name
- DAIR-AutoResearch/AutoSci★ 1.7ksame name
- PKU-DAIR/AutoSci★ 1.7ksame name
78 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.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 75 edited versions we read keep these.
6
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
- Distinctive: line 9
Verify that all 8 required outputs exist and are wired correctly after creating a new component.
- Very specific: line 22
Default values use SCREAMING_SNAKE_CASE constants above the component
- Very specific: line 29
If the component exposes a control hook, it is also exported (e.g., useCycloneControl)
- Very specific: line 54
Every example rendered on the page has a matching getExampleSource call
- Very specific: line 55
If the component has configurable props, a properties Table section exists
- Distinctive: line 56
All documented props match the actual component props (no missing, no extra)
- Distinctive: line 102
After the table, list specific issues with file paths and line numbers.
- Distinctive: line 106
If any checks have fail or warn status, fix them automatically:
- Distinctive: line 110
After all fixes, re-run the checks to confirm everything passes
- Distinctive: line 113
If a fix requires a decision (e.g., which sidebar section to place the component in), ask the user before proceeding.
“Common” is measured: kept by at least 6 in 10 of the 75 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
Check Component Skill
Verify that all 8 required outputs exist and are wired correctly after creating a new component.
Instructions
Given a component name (e.g., cyclone, MapCyclone), normalize it to its kebab-case slug (e.g., cyclone) and run through every check below.
Check 1: Component Source File
- File exists:
src/registry/map/{slug}.tsx - Has
"use client"directive (if it uses hooks, event handlers, or browser APIs) - Exports a named component (e.g.,
MapCyclone) - Uses
typenotinterfacefor type definitions - Uses arrow functions with explicit returns
- Default values use
SCREAMING_SNAKE_CASEconstants above the component - Required props come before optional props in the type definition
- Cleanup in useEffect return functions (removes layers, sources, markers, event listeners)
Check 2: Barrel Export
src/registry/map/index.tsxhas an export line for the component- If the component exposes a control hook, it is also exported (e.g.,
useCycloneControl)
Check 3: Registry Entry
registry.jsonhas an entry initemswith:namein kebab-case (e.g.,cyclone)registryDependenciesincludes"https://www.terrae.dev/map.json"files[0].pathmatches the source file pathfiles[0].targetfollowscomponents/ui/map/{slug}.tsx
Check 4: Example Files
- At least one example exists:
src/app/docs/_components/examples/{slug}-example.tsx - Examples import from
@/registry/map - Examples wrap the map in
<div className="h-full w-full"> - Examples use
process.env.NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN || ""as access token - Examples that use hooks or event handlers have
"use client"
Check 5: Documentation Page
- File exists:
src/app/docs/{slug}/page.tsx - Exports
metadatawith atitle - Uses
DocsLayoutwithtitle,description,prev, andnext - First section is "Installation" with two
CodeBlocks (base map + component) - Basic
ComponentPreviewappears directly after Installation - Every example rendered on the page has a matching
getExampleSourcecall - If the component has configurable props, a properties
Tablesection exists - All documented props match the actual component props (no missing, no extra)
Check 6: Sidebar Navigation
src/app/docs/_components/docs-sidebar.tsxhas aNavItemfor the component- The
hrefmatches/docs/{slug} - Has
badge: "new" - Placed in the correct section (
"Core"or"Features") - The Lucide icon is imported
Check 7: Components Page
src/app/docs/components/page.tsxhas aComponentItementry- The
hrefmatches/docs/{slug} - Has
isNew: true categorymatches the sidebar sectioninstallCommandURL matcheshttps://www.terrae.dev/{registry-name}.json- The Lucide icon is imported
Check 8: Changelog
src/app/docs/changelog/page.tsxhas an entry in the most recentChangelogEntry- Entry has
title,description(with<code>tag for component name), andhref hrefmatches/docs/{slug}
Output Format
Present results as a checklist table:
| # | Output | Status | Notes |
| --- | ------------------ | ------ | ----------------------- |
| 1 | Component source | pass | |
| 2 | Barrel export | pass | |
| 3 | Registry entry | fail | Missing target path |
| 4 | Examples | pass | 3 examples found |
| 5 | Documentation page | warn | Missing props: `scale` |
| 6 | Sidebar navigation | pass | |
| 7 | Components page | pass | |
| 8 | Changelog | pass | |- pass: Everything correct
- warn: Works but has minor issues (e.g., missing optional prop in docs table)
- fail: Missing or broken, needs fixing
After the table, list specific issues with file paths and line numbers.
Fix Phase
If any checks have fail or warn status, fix them automatically:
- Work through issues in check order (1–8)
- Apply the minimal change needed for each issue
- After all fixes, re-run the checks to confirm everything passes
- Present the updated checklist table showing all checks as pass
If a fix requires a decision (e.g., which sidebar section to place the component in), ask the user before proceeding.
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.

