reborn-feature

Use when building or extending a user-facing WebUI feature, endpoint, ProductSurface command/capability, or product-level API surface in the Reborn stack, or when adding/changing trigger and automation domain behavior (schedules, run-now, trigger history).

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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.

A high-quality, action-oriented feature-building skill with concrete commands, a clear validated workflow, and tight domain prose. The only notable gap is that the substantial trigger/automation invariants are inlined rather than split into a referenced file.

Suggestions

Move the detailed Automations/triggers sealed-ingress and settlement invariants into a dedicated reference file (e.g. references/automations.md) and link to it from a short summary section, tightening the main body.

Trim editorial asides like 'this class of invariant has a history of needing multiple follow-up fixes to get right' to directive guidance ('treat first-pass trigger changes as review-heavy').

The body references scripts/codebase-graph.sh but no scripts/ bundle exists; either add the script to the bundle or note that it lives in the repo so the reference is unambiguous.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence (no explaining what crates/Rust are), with every line carrying domain signal, but a few editorial passages like 'this class of invariant has a history of needing multiple follow-up fixes to get right, so treat first-pass changes here as review-heavy' could be trimmed — efficient with minor over-explanation rather than the fully lean 5.	4 / 5
Actionability	Fully executable guidance throughout: exact `rg`/`cargo test`/`cargo clippy`/`pnpm` commands, numbered implementation steps pinning specific file paths (e.g. `crates/product/ironclaw_assistant/src/reborn_services.rs`), and copy-paste-ready verification commands.	5 / 5
Workflow Clarity	Clear Before-editing → 6-step Default implementation → Verification sequence with explicit validation checkpoints (cargo test/clippy, architecture tests) and a feedback loop ('If it is missing or stale, use targeted rg searches and verify against live code').	5 / 5
Progressive Disclosure	Well-sectioned single-file skill with clearly signaled pointers to external repo docs (AGENTS.md, CLAUDE.md, CONTRACT.md, triggers.md); no bundle files exist, and the detailed Automations/triggers invariants are inlined where a one-level reference file could carry them — good structure with minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

92%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 strong, third-person trigger description that concretely enumerates capability targets and explicit use-conditions for a well-scoped internal niche. Slight headroom only in keyword/synonym breadth.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across specific targets — 'building or extending a user-facing WebUI feature, endpoint, ProductSurface command/capability, or product-level API surface' plus 'adding/changing trigger and automation domain behavior (schedules, run-now, trigger history)' — giving comprehensive coverage rather than the minor gaps of a 4.	5 / 5
Completeness	Explicitly answers both: the 'what' (building/extending WebUI features, endpoints, ProductSurface commands/capabilities, API surface, trigger/automation behavior) and the 'when' via the leading 'Use when...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with some natural synonyms (trigger/automation, schedules/run-now, trigger history), but terms are niche-technical and lack file extensions, so it stops short of the comprehensive synonym-plus-extension coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly bounded Reborn-stack niche (ProductSurface, trigger/automation domain) with distinct triggers and minimal overlap risk with generic skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: nearai/ironclaw
Path: .claude/skills/reborn-feature/SKILL.md
Commit: 94b7187

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.