place

Use when asked "where does this belong", "audit this instruction file", "why does this keep growing", or invokes /place. Read-only audit routing each clause of LLM-facing prose to a destination.

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

85%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 content is a tightly written method specification: a sequenced, validation-aware pass, a concrete output contract, and well-structured one-level-deep references. Its only weak spot is occasional over-compression that slightly taxes readability without adding clarity.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence throughout, with no padding about what skills or instruction files are; it is occasionally over-compressed to the point of requiring re-reading, keeping it just below the lean anchor.	4 / 5
Actionability	Provides a concrete 7-step pass, an explicit route-block template, and a numbered residue-extraction procedure with executable guidance, with only minor gaps (e.g., some classifier states are described abstractly rather than as copy-paste checks).	4 / 5
Workflow Clarity	The pass is a clearly sequenced multi-step process with explicit ordering rules, validation feedback loops (residue-extraction step 4 'fails silently', re-extraction after transformations), and explicit handling of destructive/batch paths via the Friction transformation and unresolved-state reporting.	5 / 5
Progressive Disclosure	SKILL.md is an overview that points to two real, clearly signaled one-level-deep reference files (routing-traces.md, evidence.md) in a dedicated Reference material section, with content appropriately split and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

95%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 exemplary: it states a precise, niche capability, gives an explicit 'Use when' clause with natural trigger phrases, and uses third-person voice throughout. It clearly answers both what the skill does and when to invoke it with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain (LLM-facing instruction prose) and several concrete actions ('audit routing', 'routing each clause ... to a destination', 'read-only audit'), with only minor coverage gaps versus a fully enumerated action list.	4 / 5
Completeness	Explicitly answers both 'what' ('Read-only audit routing each clause of LLM-facing prose to a destination') and 'when' ('Use when asked ...') with concrete trigger phrases, satisfying the top anchor.	5 / 5
Trigger Term Quality	Quotes multiple natural trigger phrases a user would actually say ('where does this belong', 'audit this instruction file', 'why does this keep growing') plus the /place invocation, giving comprehensive coverage including synonyms and a command form.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (instruction-prose placement auditing) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jongwony/epistemic-protocols
Path: epistemic-cooperative/skills/place/SKILL.md
Commit: 411e6fb

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