CtrlK
BlogDocsLog inGet started
Tessl Logo

p7

P7 Senior Engineer mode — solution-driven execution under P8 supervision. Use when user says 'P7模式', '方案驱动', or when spawned as sub-task executor by P8. Produces: implementation plan + code + 3-question self-review, delivered via [P7-COMPLETION].

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/p7/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 appropriately concise and well-structured as a thin pointer to an external protocol, but it provides little inline actionable detail and relies entirely on a cross-skill reference that may not reliably resolve from this skill's bundle.

Suggestions

Inline a minimal concrete checklist for the three phases (e.g., what '方案 + 影响分析' must contain, the exact 3 self-review questions) so the skill is actionable even if the external protocol is unavailable.

Move or copy the referenced protocol into this skill's own ./references/ directory and link it relatively, so the reference resolves within the skill bundle instead of depending on a sibling skill.

Add an explicit validation checkpoint in the workflow (e.g., 'before delivering [P7-COMPLETION], confirm the 3-question self-review passes') to make the feedback loop visible inline.

DimensionReasoningScore

Conciseness

The body is ~3 lean lines that assume Claude's competence and delegate detail to the external protocol; no padded explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It gives a high-level 3-phase sequence ('先设计方案 + 影响分析,再实施编码,完成后三问自审查') and directs loading the protocol, but all concrete execution detail is delegated to an external file with no inline specifics, fitting 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

A sequence is present (design → implement → self-review) with the 3-question self-review as a checkpoint, but validation/feedback steps are not explicit inline and are deferred to the external protocol, matching 'steps listed but validation gaps; checkpoints implicit'.

3 / 5

Progressive Disclosure

The body is a thin overview pointing to one clearly-signaled reference ('详细协议见 ../pua/references/p7-protocol.md') one level deep; good structure, though the reference resolves to a sibling skill's bundle rather than this skill's own, a minor organization gap keeping it below 5.

4 / 5

Total

15

/

20

Passed

Description

87%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 concisely states what the skill does and gives explicit, natural trigger phrases for when to use it. It is specific and highly distinct with minimal conflict risk.

DimensionReasoningScore

Specificity

Names the domain ('P7 Senior Engineer mode', 'solution-driven execution under P8 supervision') and lists several concrete outputs ('implementation plan + code + 3-question self-review, delivered via [P7-COMPLETION]'), with only minor gaps in coverage, fitting the 'several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers both 'what' (solution-driven execution producing plan + code + 3-question self-review via [P7-COMPLETION]) and 'when' ('Use when user says P7模式, 方案驱动, or when spawned as sub-task executor by P8') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would say ('P7模式', '方案驱动', 'spawned as sub-task executor by P8'); coverage is good but a few synonymous phrasings are missing, so it sits above the 3 anchor but below comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (P7 persona under P8 supervision) with distinct, specific triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

20

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.