freecodecamp-style

Author and review freeCodeCamp /news tutorials. Use when writing an fCC tutorial, a Hashnode draft, or a dual-submit checklist. It does not set kit house voice (that's `docs-writing-style`).

Quality

83%

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

85%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-structured, highly actionable instruction-only skill with clear phased workflows, validation gates, and clean one-level reference disclosure. Its main weakness is repetition of a few core rules across multiple sections, which inflates length without adding information.

Suggestions

State the dual-submit rule, the no-"-ing" headline rule, and the draft-URL-vs-preview-URL requirement once in Guardrails and reference them from the checklist and phase gates rather than restating each fully.

Consider folding the Quality checklist into the Phase gates or marking it as a recap so the same checks are not maintained in three places.

Trim the repeated "Load references before inventing rules" reminders to a single standing instruction near the top.

Dimension	Reasoning	Score
Conciseness	The body is dense and rule-focused with no over-explanation of concepts Claude already knows, but the dual-submit rule, the no-"-ing" headline rule, and the draft-URL-vs-preview-URL point each recur across Guardrails, Quick rules, Phase gates, and the Quality checklist, which could be tightened into a single source.	3 / 5
Actionability	It gives copy-paste-ready, concrete guidance — proven headline forms, slug/tag examples, the FAIL/WARN/PASS output format, a ready-to-send email body template, and a 12-item submit checklist — covering the common authoring/review/submit cases for an instruction-only skill.	5 / 5
Workflow Clarity	The Capture→Package→Draft→Integrity→Submit→Review phases are explicitly sequenced, each Phase gate is a validation checkpoint with a key question, and Review mode plus the submit checklist provide feedback loops and a checklist for a complex process.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references (publication-style-guide.md, hashnode-workflow.md, integrity-and-policy.md, review-rubric.md), each annotated with its scope, and all four files verified present in ./references/.	5 / 5
	Total	18 / 20 Passed

Description

82%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 focused, well-scoped description that cleanly states both what it does and when to use it, with explicit disambiguation from a sibling skill. It is slightly thin on the breadth of capabilities it names and could include a few more natural trigger synonyms.

Suggestions

Broaden the capability list beyond "author and review" to surface the dual-submit workflow and integrity checks as explicit actions (e.g. "Author, review, and dual-submit freeCodeCamp /news tutorials").

Add a natural synonym or two to the trigger clause, such as "freeCodeCamp article" or "/news publication", alongside "fCC tutorial".

Spell out "fCC" as "freeCodeCamp" at least once in the when clause so the trigger matches how users most often phrase the request.

Dimension	Reasoning	Score
Specificity	"Author and review freeCodeCamp /news tutorials" names the domain plus two concrete actions (author, review), matching the anchor that names a domain with 1-2 actions but is not comprehensive — it omits the dual-submit/integrity work as explicit capabilities.	3 / 5
Completeness	It explicitly answers what ("Author and review freeCodeCamp /news tutorials") and when ("Use when writing an fCC tutorial, a Hashnode draft, or a dual-submit checklist") with concrete trigger phrases, exceeding the anchor-4 example whose "when" is less specific.	5 / 5
Trigger Term Quality	"writing an fCC tutorial, a Hashnode draft, or a dual-submit checklist" gives good natural keyword coverage, but a few common variations (e.g. "freeCodeCamp article", "/news publication") are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to freeCodeCamp /news + Hashnode dual-submit, and the explicit note "It does not set kit house voice (that's `docs-writing-style`)" actively disambiguates it from a neighboring skill, giving minimal conflict risk.	5 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: saif-shines/devex-kit
Path: plugins/documentation/skills/freecodecamp-style/SKILL.md
Commit: df60de1

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.