agentleFS
Sign inStart free
DangoSysDangoSys/skills/check/SKILL.md

check

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

Validate Buckyball Ball registration consistency. Use when users ask to inspect registration status, validate a BallDomain configuration, troubleshoot registration issues, or check a registration change.

80 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • JuliusBrusseeSkill

    backprop

    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

  • skyllwtSkill

    exp-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

  • skyllwtSkill

    exp-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

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 69 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Call MCP tool validate(chip=..., balldomain?=...).

    line 8
  2. Very specific:

    Do not edit registration files during a check.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 69 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Registration Check

Call MCP tool validate(chip=..., balldomain?=...). Default chip is toy.

The tool resolves the selected BallDomain from the chip's generated topology. Registrations live under examples/threads/<thread>/configs/balldomains/, not under the chip directory. The current implementation requires the chip to resolve to one unique topology thread; for heterogeneous chips, validate each thread's BallDomain explicitly. Pass a stem such as default or a .toml path only when selecting a non-default domain.

Report the tool's pass/fail result for:

  1. ballNum equals ballIdMappings length.
  2. ballId is exactly 0, 1, 2, ... with no duplicates or gaps.
  3. ballName, funct7, and mnemonic are unique within this BallDomain.
  4. Each ISA bid exists and every Ball has at least one ISA entry.
  5. Each Ball config path exists and inBW/outBW are positive.

Expand each Ball's nested isa entries into a summary table with ballId, ballName, funct7, mnemonic, inBW, outBW, and config.

validate does not scan source headers or MLIR for hardcoded encodings. When that check is needed, inspect the relevant Ball/compiler sources separately and report it as a distinct result.

Do not edit registration files during a check. For a deterministic correction, explain the proposed change and request permission before modifying TOML; treat adding an ISA row or renumbering ballId as a semantic change, not an automatic fix.

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.

Check your setup, free