templates

Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

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

The body is well-structured as a lean dispatch overview pointing to per-template files, but every referenced TEMPLATE.md is missing from the bundle, the terminal usage step is vague, and generic boilerplate sections add token weight without value.

Suggestions

Ship the 12 referenced TEMPLATE.md files (e.g. nextjs-fullstack/TEMPLATE.md) or remove the dead links and the "Contains 12 templates" claim so progressive disclosure actually resolves.

Replace the vague step 4 ("Follow its tech stack and structure") with concrete post-read instructions or a spec of what each TEMPLATE.md must contain.

Cut the generic "When to Use" / "Limitations" boilerplate and replace it with skill-specific matching guidance to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The table and usage steps are lean and avoid explaining known concepts, but the generic "When to Use" / "Limitations" boilerplate ("applicable to execute the workflow or actions described in the overview") does not earn its place and could be tightened.	2 / 3
Actionability	The lookup table gives concrete template names, tech stacks, and a clear match procedure, but the final step "Follow its tech stack and structure" is vague and none of the referenced TEMPLATE.md files that would hold the executable steps exist in the bundle.	2 / 3
Workflow Clarity	The four-step usage sequence is clearly ordered and the single dispatch action is unambiguous, but the terminal step is vague and there is no check confirming the correct template was selected.	2 / 3
Progressive Disclosure	The body is well-organized with a clearly signaled one-level-deep table of template links, but all 12 referenced TEMPLATE.md files are missing from the bundle, so the disclosure is structurally sound yet non-functional in practice.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 clearly answers both what and when with an explicit trigger, but its capability list and trigger-term coverage are thin and the tech stacks are not enumerated, which limits specificity and distinctiveness.

Suggestions

Enumerate concrete actions (e.g. "scaffold, configure, and bootstrap") and name representative tech stacks (Next.js, FastAPI, Expo) to lift specificity beyond a single action.

Add the natural tech-stack trigger terms users actually say (e.g. "Next.js app", "FastAPI API", "Expo mobile app") alongside "creating new projects from scratch".

Replace "various tech stacks" with the specific stacks offered to reduce overlap with general coding skills and sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ("Project scaffolding templates for new applications") and a single action but does not list multiple concrete actions, matching the "names domain and some actions, but not comprehensive" anchor rather than the multi-action anchor 3.	2 / 3
Completeness	It states what it does ("Project scaffolding templates for new applications") and gives an explicit "Use when creating new projects from scratch" trigger, clearly answering both what and when.	3 / 3
Trigger Term Quality	"Use when creating new projects from scratch" is a natural trigger, but coverage is thin and the specific tech-stack terms a user would say (e.g. "Next.js app", "FastAPI") are absent, fitting "some relevant keywords but missing common variations."	2 / 3
Distinctiveness Conflict Risk	The greenfield-scaffolding niche is somewhat distinct, but "various tech stacks" is generic and the stacks are not enumerated, leaving overlap risk with general build/coding skills rather than a clear distinct niche.	2 / 3
	Total	9 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 12 missing	Warning

	Total	14 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

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