ctx

Load PRD, FRD, Tech Spec, or RFC into context

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/product-design/skills/ctx/SKILL.md

Quality

Content

77%

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

This skill provides excellent actionable guidance with clear workflows and concrete examples for loading project documents. The main weakness is verbosity - the extensive inline examples, repeated command variations, and detailed tables could be condensed or split into reference files. The skill effectively handles edge cases like multiple matches and missing documents.

Suggestions

Condense the Examples section - many examples are redundant with earlier content (e.g., loading by ID is shown 3+ times)

Move the detailed Document Type Detection rules and Options table to a separate REFERENCE.md file, keeping only essential patterns inline

Combine the multiple output format examples into a single representative example with brief notes about variations

Dimension	Reasoning	Score
Conciseness	The skill is moderately verbose with some unnecessary detail. The extensive tables, multiple example blocks, and repeated patterns (like showing the same command variations multiple times) could be condensed. However, it avoids explaining basic concepts Claude already knows.	2 / 3
Actionability	Provides concrete, executable guidance with specific search patterns, file paths, command examples, and exact output formats. The tables clearly map prefixes to locations, and the examples section shows copy-paste ready commands.	3 / 3
Workflow Clarity	The 5-step execution flow is clearly sequenced with explicit handling for multiple matches, error cases, and related document discovery. Each step has clear inputs and outputs, and the workflow includes user prompts for disambiguation.	3 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but it's a monolithic document that could benefit from splitting detailed reference tables and examples into separate files. The 200+ lines of inline content makes it harder to scan quickly.	2 / 3
	Total	10 / 12 Passed

Description

32%

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 identifies a clear domain (specification documents) but is too terse to be effective for skill selection. It lacks explicit trigger guidance and doesn't explain the full scope of what the skill can do beyond loading documents. The acronyms provide some distinctiveness but may not match how all users phrase their requests.

Suggestions

Add a 'Use when...' clause specifying triggers like 'when user asks to review requirements', 'analyze specifications', or 'load project documentation'

Expand trigger terms to include full phrases: 'product requirements document', 'functional requirements', 'technical specification', 'design documents'

Describe additional capabilities beyond loading, such as 'summarize requirements', 'extract key decisions', or 'identify dependencies'

Dimension	Reasoning	Score
Specificity	Names specific document types (PRD, FRD, Tech Spec, RFC) and one action (load into context), but only describes a single action rather than multiple concrete capabilities.	2 / 3
Completeness	Describes what it does (loads documents into context) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant acronyms (PRD, FRD, RFC) and 'Tech Spec' that users might say, but missing common variations like 'product requirements', 'functional requirements', 'technical specification', 'request for comments', or 'design doc'.	2 / 3
Distinctiveness Conflict Risk	The specific document types (PRD, FRD, Tech Spec, RFC) provide some distinctiveness, but 'load into context' is generic and could overlap with other document-loading skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 5 months 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.