docs-guide

Docs Guide Agent. 튜토리얼, 사용 가이드 작성을 담당합니다.

Install with Tessl CLI

npx tessl i github:shaul1991/shaul-agents-plugin --skill docs-guide

What are skills?

Quality

11%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/docs-guide/SKILL.md

SKILL.md

Review

Evals

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too brief and vague to effectively guide skill selection. It lacks concrete actions, natural trigger terms, and explicit 'when to use' guidance. The Korean language description provides minimal information that would help Claude distinguish this skill from other documentation or writing-related skills.

Suggestions

Add a 'Use when...' clause with specific triggers like 'when user asks for tutorials, documentation, getting started guides, how-to instructions, or README files'

List concrete actions such as 'Creates step-by-step tutorials, writes user guides with examples, structures documentation with clear sections, adds code snippets and screenshots'

Include natural keyword variations users might say: 'docs', 'documentation', 'how-to', 'walkthrough', 'onboarding guide', 'README', 'quickstart'

Dimension	Reasoning	Score
Specificity	The description only mentions '튜토리얼, 사용 가이드 작성' (writing tutorials and user guides) which is vague and abstract. No concrete actions like 'create step-by-step instructions', 'add code examples', or 'structure documentation sections' are specified.	1 / 3
Completeness	The description weakly addresses 'what' (writes tutorials and guides) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' statement to help Claude know when to select this skill.	1 / 3
Trigger Term Quality	Contains only generic terms '튜토리얼' (tutorial) and '사용 가이드' (user guide). Missing natural variations users might say like 'documentation', 'how-to', 'getting started', 'README', 'docs', or file extensions.	1 / 3
Distinctiveness Conflict Risk	While 'Docs Guide Agent' suggests documentation focus, the vague description could overlap with general writing skills, README generators, or technical documentation tools. The tutorial/guide focus provides some distinction but not enough specificity.	2 / 3
	Total	5 / 12 Passed

Implementation

14%

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

This skill is essentially a role description rather than actionable guidance. It tells Claude what to produce but not how to produce it, lacking any concrete instructions, templates, examples, or workflows for creating documentation. The content would not enable Claude to consistently produce quality tutorials or guides.

Suggestions

Add a concrete workflow with steps for creating documentation (e.g., 1. Identify audience, 2. Outline structure, 3. Write draft, 4. Validate with checklist)

Include a template or example structure for tutorials and guides showing expected format and sections

Add specific writing guidelines or style requirements (e.g., code example requirements, heading conventions, tone)

Reference or link to any existing style guides, templates, or example documents in the repository

Dimension	Reasoning	Score
Conciseness	The content is brief and doesn't over-explain concepts Claude knows, but it's so minimal that it lacks substance rather than being efficiently dense with useful information.	2 / 3
Actionability	The skill provides no concrete guidance on HOW to write tutorials, guides, or FAQs. It only lists responsibilities and output locations without any executable instructions, templates, or examples.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps for creating documentation, no validation checkpoints, and no process for reviewing or publishing guides.	1 / 3
Progressive Disclosure	The content is a flat list with no structure for discovery. It mentions output directories but provides no links to templates, style guides, or examples that would help Claude perform the task.	1 / 3
	Total	5 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

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