delete-initial-resource

Remove one or more of the initial CRM resources (contacts, companies, deals, tags, tasks) from the codebase. Use when the user asks to delete, remove, or strip out one or several of these built-in resources. Runs the delete-initial-resource.ts script to drop each resource's own folder, then guides cleanup of every file that references them.

Quality

95%

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

96%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 dense, expert-grade body: every token is project-specific knowledge, commands are executable, and the destructive workflow is gated by confirmation and layered validation with genuine feedback loops. The single soft spot is that the main SKILL.md carries nearly all shared detail inline, making it heavy for an always-loaded overview.

Suggestions

Move the file-by-file Shapes and Backend enumerations (exact .sql filenames, per-shape dependent-file lists) into a shared reference file (e.g., shapes.md / backend.md), keeping only the shape taxonomy and one example per shape in SKILL.md.

Consolidate the thrice-repeated grep-blindness warning (Shapes, Rationalizations, Verification) into the Verification section with a pointer from the others, trimming a few lines without losing the check.

Dimension	Reasoning	Score
Conciseness	Zero filler or concept explanations — no library tutorials or basic-knowledge padding; every line carries codebase-specific knowledge (grep-invisible nb_<resource>, type-checked i18n catalogs, append-only migrations, per-file SQL responsibilities). Repeated warnings appear across sections, but each repetition serves a distinct phase (discovery, rationalization rebuttal, verification) rather than padding.	5 / 5
Actionability	Copy-paste-ready commands throughout: the script invocation, "make typecheck && make lint", the grep battery, "npx supabase db diff --local -f remove_<resource>", "npx supabase db reset --local", and a sed fallback for the literal-escape Edit failure. Exact file paths (06_grants.sql, root/defaultConfiguration.ts, misc/useImportFromJson.ts) make the editing guidance concrete rather than abstract.	5 / 5
Workflow Clarity	A clear four-step sequence gated by an explicit irreversible-confirmation checkpoint, with strong validation for a destructive operation: typecheck+lint, separate targeted greps, db reset replay, a six-item checklist, and feedback loops ("Resolve whatever tsc surfaces", Edit→sed fallback, db reset catching what db diff misses). The destructive-skill validation cap does not apply — validation is thorough.	5 / 5
Progressive Disclosure	References are one level deep and clearly signaled (per-resource files annotated "spine"/"spine/link", plus cross-skill pointers to backend-dev and writing-migrations). Not a 5: the main file itself is ~97 very dense lines, and the Shapes and Backend enumerations (exact .sql filenames, per-shape file lists) could partially move into reference files to slim the always-loaded surface.	4 / 5
	Total	19 / 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.

An exemplary description: third-person voice, enumerated targets, explicit trigger synonyms, and a clear statement of the script-driven mechanism. The only minor gap is that the breadth of the cleanup work (i18n, backend SQL, verification) is compressed into a single "guides cleanup" clause.

Dimension	Reasoning	Score
Specificity	Names the domain (the five initial CRM resources, enumerated) and several concrete actions: "Runs the delete-initial-resource.ts script to drop each resource's own folder, then guides cleanup of every file that references them." Not a 5 because the cleanup half is summarized as "guides cleanup" without hinting at the i18n, dataProvider, or Supabase scope the body shows are major parts of the work.	4 / 5
Completeness	Clearly answers both: the "what" (remove resources, script drops folders, cleanup of every referencing file) and an explicit "Use when the user asks to delete, remove, or strip out one or several of these built-in resources" trigger clause with concrete phrases — matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	"delete, remove, or strip out" covers the natural synonyms users would say, and the exact targets are enumerated by name ("contacts, companies, deals, tags, tasks"). The equivalent of file-extension coverage is present via the explicit resource list.	5 / 5
Distinctiveness Conflict Risk	"initial CRM resources" + "built-in" + the five enumerated names carve a tight niche (deletion of seeded scaffold resources in this codebase), with distinct triggers and minimal overlap with any other skill.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: marmelab/atomic-crm
Path: .claude/skills/delete-initial-resource/SKILL.md
Commit: 8b5d47b

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