reborn-extension-surfaces

Use when adding or changing a Reborn integration — a new extension, a channel surface, model-callable tools, or a shared auth provider — or when deciding whether something is "a channel", "an extension", or "a tool". Maps the unified extension model (NEA-25) to the exact manifest sections, crates, seams, and tests.

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

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.

The body is a tightly-engineered, codebase-specific guide: every section names the exact manifest keys, crate paths, trait seams, and test suites to touch, with concrete verification commands and an architecture-test gate as the closing checkpoint. It assumes Claude's competence and spends its tokens on things Claude could not infer.

Dimension	Reasoning	Score
Conciseness	Dense and almost entirely project-specific (crate paths, manifest keys, gate names) with no generic concept padding; a few definitional prose passages about the taxonomy could be tightened further, keeping it just below the lean-every-token-earns-its-place anchor.	4 / 5
Actionability	Provides copy-paste-ready commands ('grep -c ^\[\[tools\]\]', 'cargo test -p ironclaw_architecture_tests', 'pnpm --dir ... test') alongside exact crate, trait, and test-file paths, with exemplar manifests named for each surface type.	5 / 5
Workflow Clarity	Each surface type has a numbered, sequenced workflow with explicit validation checkpoints (architecture-tests gate, conformance suites, frontend tests), and destructive identity-rename/migration operations are guarded by the boot-restore contract and retired-taxonomy gate.	5 / 5
Progressive Disclosure	Acts as an overview that points to one-level-deep, clearly-signaled codebase references (exemplar manifests, design docs, trait homes, sibling skills) via exact paths, with well-organized sections and no nested reference chains.	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.

The description is a strong, concrete trigger-and-scope statement: it names the exact integration surfaces, gives an explicit 'Use when' clause covering both build and taxonomy-decision cases, and is tightly scoped to this codebase's extension model. It would reliably surface for the right tasks and not for unrelated ones.

Dimension	Reasoning	Score
Specificity	Enumerates concrete capability areas — 'a new extension, a channel surface, model-callable tools, or a shared auth provider' — and the mapping function 'to the exact manifest sections, crates, seams, and tests', listing several specific actions rather than vague language.	4 / 5
Completeness	Explicitly answers both 'what' (maps the unified extension model to manifest sections, crates, seams, and tests) and 'when' ('Use when adding or changing a Reborn integration ... or when deciding whether something is ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers the natural taxonomy terms a developer would say ('extension', 'channel surface', 'tools', 'auth provider', and the decision triggers 'a channel / an extension / a tool') with good synonym coverage, though internal jargon like 'NEA-25' narrows the natural-phrase reach.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche around Reborn extension surfaces and the channel/extension/tool taxonomy decision, with minimal overlap risk against sibling skills that cover feature-wiring, testing, or boundaries.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nearai/ironclaw
Path: .claude/skills/reborn-extension-surfaces/SKILL.md
Commit: 9102166

Reviewed: 1 day 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.