CtrlK
BlogDocsLog inGet started
Tessl Logo

ironclaw-reborn-testing

Use when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.

79

Quality

100%

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

100%

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

A tight, expert-aimed decision layer that routes test work to the right tier with concrete commands, repo-specific traps, and a well-signaled companion reference. It assumes Claude's competence and concentrates entirely on non-obvious project knowledge.

DimensionReasoningScore

Conciseness

Lean and dense with repo-specific knowledge Claude lacks (tier routing, traps, exact paths); it never explains basic concepts like what a unit test or Postgres is, so every token earns its place.

3 / 3

Actionability

Provides concrete executable commands and paths — 'cargo test --features integration', 'grep -n integration .github/workflows/platform-and-compat.yml', 'bash scripts/reborn-e2e-rust.sh' — alongside specific file targets per tier.

3 / 3

Workflow Clarity

The numbered tier decision tree and sequenced Verify pipeline give a clear routing sequence, with explicit re-verify checkpoints ('re-verify: grep …', 'run it locally when your change is DB/runtime-shaped') acting as validation gates.

3 / 3

Progressive Disclosure

Well-organized sections form a concise overview, and the single one-level-deep reference [references/exemplar-tests.md] is clearly signaled and verified present, keeping detail out of the main file.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, trigger-rich description that cleanly states capability and usage conditions in third-person imperative form without padding. It is distinctive and free of fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'choosing a test tier, covering a bug fix, testing model/tool-choice behavior' — rather than vague language, matching the top anchor.

3 / 3

Completeness

Explicitly answers both what (testing/reviewing Reborn behavior) and when via an explicit 'Use when …' clause with enumerated triggers.

3 / 3

Trigger Term Quality

Covers natural terms a developer would actually say — 'bug fix', 'Postgres', 'Docker', 'live LLM', 'tests/integration' — with good breadth of variations.

3 / 3

Distinctiveness Conflict Risk

'Reborn behavior' plus repo-specific paths (tests/integration, tests/fixtures/llm_traces) carves a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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: 3 missing, 1 deeper-than-1-level

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.