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

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/fractal-file-structuring/SKILL.md

Quality

Content

75%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-crafted, self-contained instruction skill: concrete examples, clear rules, and a useful decision checklist make it directly actionable. The main weaknesses are mild redundancy between the rules and checklist sections and the absence of an explicit verification step for moves/splits.

Suggestions

Add a verification checkpoint to the Decision Checklist (e.g., after a move/split, confirm imports still resolve and tests pass) to strengthen workflow clarity for a structurally risky operation.

Trim redundancy between the Core Rules and the Decision Checklist / When Unsure sections so each section earns its tokens distinctly.

Consider extracting the larger folder-tree examples into a short reference file to push progressive disclosure toward fully separated detail.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, assumes Claude's competence (it never explains what TypeScript or imports are), and earns its tokens, but the opening line restates the description and the Decision Checklist / When Unsure sections recapitulate the Core Rules, adding minor redundancy.	4 / 5
Actionability	Concrete file-name examples, real TypeScript import snippets, and explicit folder-tree diagrams give mostly executable guidance with only minor gaps (no scripted/automated commands), which fits an instruction-only skill well.	4 / 5
Workflow Clarity	The numbered Decision Checklist and the "When Unsure" branching guidance provide a clear sequenced process for placement decisions, though there is no explicit verification checkpoint (e.g., confirming imports still resolve after a move).	4 / 5
Progressive Disclosure	The single self-contained SKILL.md is well-structured with clear section headers (Scope, Core Rules, Decision Checklist, When Unsure) and easy navigation; no external references are needed, though at ~170 lines some illustrative examples could optionally be split into a reference file.	4 / 5
	Total	16 / 20 Passed

Description

83%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 description: it leads with an explicit "Use when" trigger, names concrete actions, and carves out a clear (if slightly overlapping) niche. It is held back from a perfect mark only by missing a few natural synonyms and minor overlap with generic refactoring guidance.

Suggestions

Add synonyms like "refactor" or "restructure" and file extensions (.ts, .tsx) to broaden natural trigger coverage.

Tighten the trailing parenthetical "(once the structure is established and understood)" which adds little trigger value and pads the description.

Sharpen distinctiveness by foregrounding the fractal-tree methodology earlier so it reads less like generic file-organization advice.

Dimension	Reasoning	Score
Specificity	The description enumerates several concrete actions ("creating, moving, splitting, or organizing TypeScript files and folders") plus the applied methodology, which is several specific actions with minor coverage gaps rather than a fully comprehensive capability list.	4 / 5
Completeness	It explicitly states the "when" via a "Use when creating, moving, splitting, or organizing..." clause with concrete triggers and the "what" via "Applies fractal tree file-structuring rules which reduce the cognitive overhead of choosing where to put files", satisfying both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger terms (create, move, split, organize, files, folders, TypeScript) align well with what a user would say, though it omits common synonyms like "refactor"/"restructure" and file extensions (.ts, .tsx).	4 / 5
Distinctiveness Conflict Risk	The TypeScript/JavaScript plus fractal-tree niche is fairly distinct, but the broad create/move/split/organize-file triggers carry minor overlap risk with general refactoring or code-organization skills.	4 / 5
	Total	17 / 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
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: 0144f9c

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.