CtrlK
BlogDocsLog inGet started
Tessl Logo

ironclaw-reborn-architecture-review

Use when writing or reviewing a change in crates/ that adds a trait, a crate, a dependency edge, a re-export, or code in ironclaw_composition — or when deciding whether an abstraction, layer, or crate boundary is justified in the IronClaw Reborn stack.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplar review-checklist skill: executable commands, exact file:line anchors, an explicit verification section, and a single well-signaled reference file. The only room for improvement is light tightening of a few long checklist items.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence — no basic Rust/crate explanations — but several checklist items are long paragraphs and the 'don't trust a hardcoded number here' refrain recurs, so minor trimming is possible.

4 / 5

Actionability

Copy-paste ready commands throughout ('cargo test -p ironclaw_architecture_tests', 'rg -o ...', 'grep -n ARCH-SPRAWL ...') plus exact file:line references like 'ironclaw_agent_loop/src/planner.rs:15-26' cover the common cases.

5 / 5

Workflow Clarity

A six-item checklist ('run all six; each is checkable') with embedded validation per item, a closing Verify section with feedback commands, and a rationalizations table that serves as an error-recovery aid.

5 / 5

Progressive Disclosure

Lean ~25-line overview organized into clear sections with a single well-signaled one-level reference ('references/worked-examples.md — the living curriculum'), which is a real file in the bundle.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tightly scoped, well-triggered description that names concrete architectural constructs and gives an explicit 'Use when' clause. The only soft spot is that the action verbs ('writing or reviewing') are generic compared to the very specific trigger objects.

DimensionReasoningScore

Specificity

Lists several concrete trigger objects — 'a trait, a crate, a dependency edge, a re-export, or code in ironclaw_composition' — but the verbs 'writing or reviewing' are generic, leaving minor gaps versus fully comprehensive action coverage.

4 / 5

Completeness

Explicitly answers both what (writing/reviewing architectural changes, judging abstractions/boundaries) and when via a concrete 'Use when...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of the domain's natural vocabulary ('trait', 'crate', 'dependency edge', 're-export', 'abstraction', 'layer', 'crate boundary'), with a few natural synonyms (e.g. 'module', 'interface') absent.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to 'crates/', 'ironclaw_composition', and the 'IronClaw Reborn stack' — a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
nearai/ironclaw
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.