fractal-file-structuring

Use when creating, moving, splitting, or organizing TypeScript files and folders. Applies fractal tree file-structuring rules which reduce the cognitive overhead of choosing where to put files and ultimately navigating a codebase (once the structure is established and understood).

Quality

88%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and clearly sequenced with concrete file-tree and import examples plus a decision checklist. Its main weaknesses are length — the same editor-view scaffold is repeated across several sections — and a monolithic single-file structure that could offload detailed examples to a reference.

Suggestions

Consolidate the four editor-view tree examples into a single progressive example (or one per rule without re-scaffolding the same tree) to cut repeated prose and tokens.

Move the detailed worked examples and import do/don't blocks into a referenced file (e.g. EXAMPLES.md) and keep SKILL.md as a lean overview of the core rules, decision checklist, and when-unsure guidance.

Trim restated rules where the file-tree comments already convey the constraint (e.g. the private-subtree import rule is explained both in prose and via the Avoid/Prefer import block).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the editor-view tree is reused across four sections and some prose restates rules already conveyed by the trees, so it could be tightened rather than earning the 3-anchor's every-token-earns-its-place bar.	2 / 3
Actionability	Concrete kebab-case examples, real file-tree layouts, copy-paste TypeScript import do/don't blocks, plus a numbered Decision Checklist make the guidance fully executable and specific, matching the 3-anchor.	3 / 3
Workflow Clarity	A sequenced 7-step Decision Checklist and a When Unsure decision tree give a clear placement workflow; this is non-destructive guidance so the missing-validation cap does not apply, clearing the 3-anchor over the implicit-checkpoint 2-anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers and no deep nesting, but the skill is a ~170-line monolithic file with no references; the detailed worked examples could be split into a reference to keep the overview lean, matching the 2-anchor over the one-level-deep 3-anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong: it opens with an explicit Use when trigger, names concrete actions and the TypeScript domain, and stakes out a distinctive fractal-structuring niche. The only minor weakness is mild padding in the second sentence, which does not affect the scored dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "creating, moving, splitting, or organizing TypeScript files and folders" — matching the anchor for several specific concrete actions rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both what ("Applies fractal tree file-structuring rules") and when ("Use when creating, moving, splitting, or organizing..."), satisfying the 3-anchor requirement for an explicit Use when trigger.	3 / 3
Trigger Term Quality	Uses natural terms a user would say (create/move/split/organize files and folders, TypeScript) with good coverage; not merely jargon, so it clears the 3-anchor bar over the 2-anchor "missing common variations."	3 / 3
Distinctiveness Conflict Risk	The fractal-tree file-placement niche for TypeScript is a clear, distinct trigger set unlikely to fire for unrelated skills, matching the 3-anchor rather than the overlapping 2-anchor.	3 / 3
	Total	12 / 12 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: hashintel/hash
Path: .claude/skills/fractal-file-structuring/SKILL.md
Commit: 4f2d2ce

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