chatto-architecture-inventory

Maintain Chatto's current runtime architecture inventory in docs/architecture/. Use when adding, changing, removing, auditing, or documenting runtime components, projections or snapshots, NATS and JetStream resources, subject namespaces and event types, runtime-state keys, durable effects, ConnectRPC or Operator API mounts, or realtime delivery architecture. By default, inspect the codebase, apply all in-scope inventory fixes, and validate them; report without editing only when the user or parent workflow explicitly requests an audit, review, report, or propose-only result.

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 well-structured, highly actionable instruction-only skill body with clear workflows, an explicit validation checklist, and a defined completion condition. Conciseness and progressive disclosure are strong but have minor room to improve via deduplication and possible reference splitting.

Suggestions

Consolidate the repeated maintenance-vs-report-only and category-scoped-audit guidance into one section to remove redundancy across Action mode, Start here, and Validation.

Consider extracting the per-category routing details (source files and fields to record) into a reference file referenced one level deep, keeping SKILL.md as a shorter overview.

Dimension	Reasoning	Score
Conciseness	Lean, imperative guidance that assumes Claude's competence and avoids explaining known concepts, but the maintenance-vs-report-only message and the "do not do a full audit for category-scoped changes" point recur across Action mode, Start here, and Validation, so minor tightening is possible.	4 / 5
Actionability	Concrete and executable throughout: specific output files (docs/architecture/runtime-components.md), specific source files and methods to consult (NewChattoCore, Subjects(), CreateOrUpdateStream, API.Handlers(), projection_subjects_test.go), per-category fields to record, and a concrete command (mise license-check).	5 / 5
Workflow Clarity	Clear sequenced workflows (Start here, maintenance-mode 4-step flow) with an explicit Validation checklist and a defined completion condition ("no known in-scope documentation drift remains") that establishes the validate-fix loop for a batch documentation operation.	5 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and no nested references, but at ~200 lines some category-specific detail could arguably live in separate reference files; navigation is still easy.	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, specific description that clearly states what the skill does and when to use it, with comprehensive scope enumeration and low conflict risk. Trigger term coverage is very good though a few natural synonyms are missing.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ("Maintain Chatto's current runtime architecture inventory in docs/architecture/") and lists multiple specific in-scope scopes (runtime components, projections/snapshots, NATS and JetStream resources, subject namespaces and event types, runtime-state keys, durable effects, ConnectRPC or Operator API mounts, realtime delivery architecture) plus concrete actions (adding, changing, removing, auditing, documenting).	5 / 5
Completeness	Explicitly answers both "what" (maintain the architecture inventory in docs/architecture/) and "when" (Use when adding, changing, removing, auditing, or documenting the listed scopes), with concrete trigger phrases and a default-behavior clarification.	5 / 5
Trigger Term Quality	The "Use when adding, changing, removing, auditing, or documenting" clause plus the enumerated entity types are natural phrases a user would say, but a few common synonyms/variations are not covered, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific codebase's architecture docs with a precise list of entity types, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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: chattocorp/chatto
Path: .agents/skills/chatto-architecture-inventory/SKILL.md
Commit: 967a9a1

Reviewed: 5 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.