p10

P10 CTO mode — define strategic direction, design org topology, manage P9 teams. Use when user says 'CTO模式', 'P10', '战略规划', '架构委员会', or when facing cross-team architectural decisions. Produces: strategic input templates + org design.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/p10/SKILL.md

Quality

Content

55%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.

The body is maximally concise and assumes Claude's competence, but it delegates nearly all actionable guidance to an external protocol file that is not present in the bundle. As a standalone SKILL.md it lacks executable workflow steps, validation checkpoints, and a verifiable reference, so actionability and workflow clarity are weak.

Suggestions

Inline at least a minimal, concrete sequence of the P10 protocol's core steps (define strategic input → design org topology → assign P9 mandates) with explicit validation checkpoints, instead of relying solely on the external file.

Either include the referenced p10-protocol.md in a ./references/ bundle and link it with a clear, resolvable path, or move the essential protocol content inline so the skill is self-contained.

Add a brief 'verify the protocol loaded' or output-validation step so the strategic-input templates and org design can be checked before completion.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean — a one-line maxim, a pointer, and one behavioral caveat — assuming Claude's competence and earning every token without over-explaining what a CTO or P9 is.	5 / 5
Actionability	Guidance is almost entirely high-level: it points to a protocol file ('加载后按协议执行') and defers to another skill rather than giving concrete, executable steps to execute in the body itself.	2 / 5
Workflow Clarity	No sequenced workflow or validation checkpoints are present in the body; the only directive is to load an external protocol, and the referenced file does not exist, leaving the process undefined.	2 / 5
Progressive Disclosure	It does point to a separate file (../pua/references/p10-protocol.md), but that reference is not clearly resolvable — the file does not exist — and navigation is a bare relative path with no in-body structure to guide discovery.	2 / 5
	Total	11 / 20 Passed

Description

100%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.

The description is strong: it states concrete capabilities, provides explicit user-facing trigger phrases in the natural language of its audience, and clearly answers both what the skill does and when to use it. It is concise and uses third person throughout, with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions — 'define strategic direction, design org topology, manage P9 teams' and outputs 'strategic input templates + org design' — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	It explicitly answers both 'what' (define strategic direction, design org topology, manage P9 teams) and 'when' ("Use when user says..." with concrete trigger phrases and a situational condition).	5 / 5
Trigger Term Quality	It includes natural user phrases a speaker would actually say ('CTO模式', 'P10', '战略规划', '架构委员会') plus the situational trigger 'cross-team architectural decisions', covering synonyms and the specific domain vocabulary.	5 / 5
Distinctiveness Conflict Risk	The P10/CTO-mode niche with its specific Chinese trigger terms and cross-team architectural framing carves a clear, narrow scope with minimal overlap against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tanweai/pua
Path: skills/p10/SKILL.md
Commit: ac50267

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