Name: personal-tool-builder
Rating: 38.4 (1 reviews)
Author: administrakt0r

personal-tool-builder

You believe the best tools come from real problems. You've built dozens of personal tools - some stayed personal, others became products used by thousands. You know that building for yourself means you have perfect product-market fit with at least one user.

Quality

36%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/personal-tool-builder/SKILL.md

The canonical home for this skill is personal-tool-builder in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

53%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 body is action-rich with solid CLI and storage code examples, but its markdown structure is broken by nested/mismatched code fences and it carries broken cross-references plus redundant persona fluff. Organization and structural integrity need cleanup to realize its otherwise good guidance.

Suggestions

Fix the malformed fenced code blocks: the 'Scratch Your Own Itch' and 'Local-First Apps' sections open fences around markdown headings and nest inner fences, breaking rendering — flatten these into prose or properly fenced examples.

Resolve the Sharp Edges cross-references by either adding the referenced sections ('Making Tools Portable', 'Taming Configuration', 'Security in Personal Tools', 'Sustainable Personal Tools') or moving that detail into reference files and linking to them.

Remove the duplicated persona opening and the vacuous closing 'When to Use' line to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly concrete and compact (tables, code), but the opening persona restates the description, the closing 'When to Use' is vacuous, and malformed nested code fences waste structural tokens.	3 / 5
Actionability	Provides concrete, mostly executable code (commander/click CLI scaffolds, JSON file storage, better-sqlite3 setup) covering common cases, with only minor gaps such as an unimported mkdirSync.	4 / 5
Workflow Clarity	A rough Day1/Week1/Month1 progression and a 10-Minute Test checklist give sequence, but there are no explicit validation checkpoints and the broken nested fences disrupt the flow.	3 / 5
Progressive Disclosure	No bundle files exist and all code/patterns are inlined; the Sharp Edges table references sections ('## Making Tools Portable', '## Taming Configuration', '## Security in Personal Tools') that do not exist in the body.	2 / 5
	Total	12 / 20 Passed

Description

20%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 reads as a motivational persona rather than a capability/trigger statement: it is second-person, abstract, and lacks both concrete actions and any 'Use when' guidance. It would not reliably surface for the right user need.

Suggestions

Rewrite in third person listing concrete capabilities, e.g. 'Builds personal productivity tools, CLI utilities, and local-first apps from real personal pain points.'

Add an explicit trigger clause: 'Use when the user wants to scratch their own itch, build a personal CLI/script tool, or prototype a local-first app for personal use.'

Replace abstract persona claims with action verbs and natural trigger terms users would actually say.

Dimension	Reasoning	Score
Specificity	The description names the domain ('personal tools', 'products') but only abstract actions ('built dozens', 'building for yourself') with no concrete capabilities, landing at anchor 2; the second-person voice ('You believe', 'You've built', 'You know') triggers a -1 penalty.	1 / 5
Completeness	It offers a vague 'what' (build personal tools) and entirely omits any 'when'/Use-when clause, matching the anchor for a vague 'what' with no 'when'.	2 / 5
Trigger Term Quality	Only a couple of generic keywords ('personal tools', 'products', 'building for yourself') appear; none are natural phrases a user would actually say when needing this skill.	2 / 5
Distinctiveness Conflict Risk	The persona-level framing ('personal tools', 'products used by thousands') is very broad and would overlap with many builder or productivity skills.	2 / 5
	Total	7 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/personal-tool-builder/SKILL.md
Commit: 57c135b

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