CtrlK
BlogDocsLog inGet started
Tessl Logo

build-resource-pages

Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.

57

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./build-resource-pages/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The body is a thorough, well-sequenced build guide with a strong validation gate, but it is verbose with repeated themes and offers little executable code. It is also a single large file with no progressive disclosure, despite being long enough to benefit from splitting.

Suggestions

Move the detailed Production Quality Standards and the Technical Checklist into reference files (e.g. references/quality-standards.md, references/pre-ship-checklist.md) and link to them from the body to improve progressive disclosure.

Collapse the repeated "production-final / no placeholders / no prototypes" statements into a single authoritative rule and remove the rest to reduce verbosity.

Add at least one concrete, executable code scaffold (e.g. a Next.js/Astro content-collection loader or an Article layout component skeleton) so the guidance is copy-paste-ready rather than purely descriptive.

DimensionReasoningScore

Conciseness

Mostly efficient and well-organized, but the "production-final" theme is restated across Workflow, Production Quality Standards, and Rules, the Technical Checklist rehashes body content, and name-dropping Stripe/Linear/Vanta/Vercel adds little executable value; could be tightened.

2 / 3

Actionability

Provides some concrete specifics — the <head> metadata HTML block, route pattern /resources/[subsection]/[slug], and typographic values (16-18px, 1.6-1.8 line height) — but the bulk is descriptive instruction about what to build rather than executable, copy-paste-ready code for the build itself.

2 / 3

Workflow Clarity

A clear three-phase sequence with ordered build sub-steps, an explicit "Report findings… before proceeding" checkpoint, and a ship-gate Technical Checklist ("Do not ship if any item fails") with per-field validation guidance — matching the anchor for clear sequence with explicit validation and a checklist.

3 / 3

Progressive Disclosure

Well-sectioned internally but monolithic — the entire ~250-line body lives in SKILL.md with no bundle files or one-level-deep references, and several blocks (detailed design standards, the checklist) could be split out for easier navigation.

2 / 3

Total

9

/

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 is specific and distinctive, naming concrete deliverables and a clear niche. Its main weakness is the absence of an explicit trigger clause, which leaves the "when to use it" question only implied and caps completeness and trigger-term quality.

Suggestions

Add an explicit "Use when…" clause naming natural trigger phrases, e.g. "Use when building or standing up a resource center (blog, guides, learn, or comparisons pages) from existing markdown on a client site."

Include common natural-language variations users would say — "resource center", "content hub", "build blog/guides pages" — to improve trigger-term coverage.

Lead with the trigger condition before the capability list so the "when" is as prominent as the "what".

DimensionReasoningScore

Specificity

Names multiple concrete actions — "builds production-final resource center pages", "Implements hub pages, section listings, article pages, and cross-linking" — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers "what" (builds resource center pages from existing markdown) but provides no explicit "when to use it" clause; per the judging guidelines a missing "Use when…" clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant domain keywords ("resource center pages", "Blog, Guides, Learn, and Comparisons", "markdown files") but lacks a "Use when…" trigger phrasing and common natural variations, so coverage is partial rather than complete.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — building resource centers from existing content markdown on a client's own tech stack/design system — with distinct triggers unlikely to activate the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
onvoyage-ai/gtm-engineer-skills
Reviewed

Table of Contents

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.