docs-internal

Docs Internal Agent. 아키텍처 문서, 온보딩 가이드 작성을 담당합니다.

Quality

35%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

37%

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

This skill content is essentially a role description rather than an actionable skill. While it's concise and well-structured, it completely lacks the concrete guidance, templates, examples, or workflows needed for Claude to actually create quality internal documentation. The skill tells Claude WHAT to produce but not HOW to produce it.

Suggestions

Add concrete templates or examples for each document type (architecture doc template, ADR template, onboarding guide structure)

Define a clear workflow for creating each document type with validation steps (e.g., 1. Gather requirements 2. Draft outline 3. Review checklist 4. Write content)

Include specific formatting guidelines, required sections, and quality criteria for each document type

Add references to example documents or style guides in the output directories

Dimension	Reasoning	Score
Conciseness	The content is extremely lean with no unnecessary explanation. Every line serves a purpose - role definition, task list, and output locations. No padding or concepts Claude already knows.	3 / 3
Actionability	The skill provides no concrete guidance on HOW to perform any of the listed tasks. It only describes what the agent does without any executable instructions, templates, examples, or specific steps for creating architecture docs, onboarding guides, or ADRs.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps for creating any of the document types, no validation checkpoints, and no process for how to approach documentation tasks. Simply listing document types is not a workflow.	1 / 3
Progressive Disclosure	The content is well-organized with clear sections, but it lacks any references to detailed materials. For a documentation agent, there should be links to templates, style guides, or example documents in the referenced directories.	2 / 3
	Total	7 / 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.

This description provides a basic understanding of the skill's domain (internal documentation) but lacks the explicit trigger guidance required for Claude to reliably select it from a large skill pool. The Korean-only content limits discoverability, and the absence of concrete actions or a 'Use when...' clause significantly weakens its utility for skill selection.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'architecture documentation', 'onboarding guide', 'internal docs', '아키텍처', '온보딩'

List specific concrete actions such as 'Creates architecture diagrams, writes onboarding documentation, maintains internal wikis'

Include both Korean and English trigger terms to improve discoverability across language contexts

Dimension	Reasoning	Score
Specificity	Names the domain (documentation) and mentions two specific document types (architecture documents, onboarding guides), but uses vague action '작성을 담당합니다' (is responsible for writing) rather than listing concrete actions like 'creates', 'updates', 'reviews'.	2 / 3
Completeness	Describes what it does (writing architecture docs and onboarding guides) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant Korean terms like '아키텍처 문서' (architecture documents) and '온보딩 가이드' (onboarding guides), but lacks common variations, English equivalents, or natural phrases users might say when requesting documentation help.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to internal documentation with architecture and onboarding focus, but 'Docs Internal Agent' is generic enough to potentially conflict with other documentation-related 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

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