engram-project-structure

Repository structure and placement rules for Engram. Trigger: Creating files, packages, handlers, templates, styles, or tests in this repo.

Quality

82%

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

86%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 lean, well-organized placement guide that delivers concrete, actionable rules with specific repo paths and clear decision mappings. It loses a little on actionability and workflow clarity due to a few abstract rules and the absence of any verification step.

Suggestions

Tighten the one abstract rule ("Put behavior near its domain") with a one-line concrete example showing the correct placement.

Add a brief verification note (e.g., "Confirm new files live in the package named in the matching rule") to give the placement decision a lightweight checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is ~30 lines with no padding and no explanation of concepts Claude already knows; every rule earns its place and assumes Claude's competence.	5 / 5
Actionability	Concrete guidance with specific paths (e.g., "internal/cloud/dashboard/*.templ", "store/cloudstore") and clear if-then mappings, but a few rules stay abstract ("Put behavior near its domain") and there are no executable commands.	4 / 5
Workflow Clarity	The "File Creation Rules" section gives unambiguous New X -> Y decision mappings and the placement rules are well-ordered, but there is no multi-step sequence or validation checkpoint (none is strictly needed for placement guidance).	4 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the content is split into four well-organized, clearly headed sections (When to Use, Placement Rules, File Creation Rules, Anti-Patterns), satisfying the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

78%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 well-structured description that clearly answers both what and when with an explicit, concrete trigger clause. It is mostly distinct thanks to repo scoping, though the capability statement is generic and trigger terms lack synonyms or extensions.

Suggestions

Replace the generic capability phrase "placement rules" with concrete actions such as "Decide where to place packages, handlers, templates, styles, and tests".

Add synonyms and file extensions to the trigger (e.g., ".templ", ".css", "_templ.go") to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Repository structure and placement rules for Engram" names the domain but describes capability only generically ("rules"), while the trigger enumerates concrete entities (files, packages, handlers, templates, styles, tests) without listing multiple distinct actions.	3 / 5
Completeness	It explicitly states what ("Repository structure and placement rules for Engram") and an explicit when prefixed with "Trigger:" followed by concrete trigger phrases, satisfying both requirements.	5 / 5
Trigger Term Quality	"Creating files, packages, handlers, templates, styles, or tests" gives good natural keyword coverage a user would say, but lacks synonyms and file extensions needed for a 5.	4 / 5
Distinctiveness Conflict Risk	Scoping to the named Engram repo gives a clear niche with minimal conflict, but the generic triggers (creating files/packages) retain minor overlap risk with other scaffolding or convention skills.	4 / 5
	Total	16 / 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: Gentleman-Programming/engram
Path: skills/project-structure/SKILL.md
Commit: 47f281c

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