CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 clean, token-efficient delegation layer that clearly signals its single external protocol reference and defers behavioral rules to the /pua parent skill. Its only weakness is actionability: the body carries no executable specifics of its own, relying entirely on an out-of-bundle protocol file.

Suggestions

Inline a 2-3 line summary of the protocol's core steps or a minimal strategic-input template so the skill is actionable even before the external protocol file is loaded.

Note that the referenced protocol lives outside this skill's bundle (../pua/references/p10-protocol.md); confirm that path is stable/available, or vendor a local copy under ./references/ so the skill is self-contained.

Briefly name the '/pua 三条红线 and 旁白协议' so a reader need not load the parent skill to know which behavioral constraints apply.

DimensionReasoningScore

Conciseness

The body is a lean four-line overview with a one-line epigraph and two pointer lines — every token earns its place and nothing explains concepts Claude already knows; not a 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

It gives a concrete directive ('详细协议见...加载后按协议执行' names a specific file and instructs loading + executing per protocol) but the body itself contains no executable specifics, delegating everything to an external file outside this bundle; not a 3 because no in-body concrete steps or examples are present, and not a 1 because it does instruct rather than merely describe.

2 / 3

Workflow Clarity

As a simple single-purpose delegating skill (well under 50 lines), its single action — load p10-protocol.md and execute per protocol while following /pua's red lines and aside protocol — is unambiguous; the simple-skills carve-out applies, so it is not capped at 2.

3 / 3

Progressive Disclosure

SKILL.md is an appropriately thin overview pointing to a single clearly-signaled, one-level-deep reference ('详细协议见 ../pua/references/p10-protocol.md') with content correctly kept out of the body; not a 2 because the reference is explicitly signaled and nothing that should be separate is inline.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concisely names concrete capabilities, declares explicit outputs, and provides an explicit 'Use when' trigger with natural-language terms a user would actually say. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'define strategic direction, design org topology, manage P9 teams' — plus explicit outputs ('strategic input templates + org design'), matching the 'lists multiple specific concrete actions' anchor; not a 2 because it is comprehensive rather than naming only a domain and a few actions.

3 / 3

Completeness

Explicitly states both what it does ('define strategic direction... manage P9 teams... Produces: strategic input templates + org design') and when to use it via an explicit 'Use when...' trigger clause; not a 2 because the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

The 'Use when user says CTO模式, P10, 战略规划, 架构委员会, or when facing cross-team architectural decisions' clause gives natural phrasings a user would actually say; not a 2 because it covers several common variations rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

The P10/CTO strategic-layer niche with language-specific triggers (CTO模式, 架构委员会) is clearly distinguishable from other skills and unlikely to fire for the wrong one; not a 2 because the triggers are distinctive rather than broadly overlapping.

3 / 3

Total

12

/

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
tanweai/pua
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.