CtrlK
BlogDocsLog inGet started
Tessl Logo

gstack-openclaw-ceo-review

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

62

Quality

72%

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 ./openclaw/skills/gstack-openclaw-ceo-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, highly actionable review procedure with explicit approval gates and a defined output format. Its weakness is token efficiency: motivational framing and an 18-item list of familiar CEO heuristics pad the body, and some catalog content would be better split into reference files.

Suggestions

Trim the Philosophy section's metaphor framing and compress or cut the 18 'Cognitive Patterns' — Claude already knows these heuristics; keep only the handful that genuinely shape review posture (e.g., inversion reflex, subtraction default).

Move the per-section detail for the 11 review sections (or the mode-specific Step 0 analyses) into a references/ file, keeping SKILL.md as a lean overview with one-level-deep pointers.

Add one short worked example of a single finding (issue → question to user → resolution) so the 'one issue at a time' interaction pattern is concrete rather than described.

DimensionReasoningScore

Conciseness

The body is dense and directive, but the Philosophy section leans on metaphor prose ('You are building a cathedral', 'You are a surgeon') and the 18-item 'Cognitive Patterns' list largely restates CEO-thinking concepts Claude already knows ('People, products, profits... always in that order', 'Fast is default'), so noticeable portions could be trimmed without losing guidance value.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: named exceptions with rescue actions and user-visible outcomes, an effort/risk taxonomy (S/M/L/XL, Low/Med/High) for alternatives, per-section checklists, an exact output template, and defined completion statuses. Minor gaps: no worked example of a finding or summary.

4 / 5

Workflow Clarity

A clear sequence runs Step 0 (premise challenge, alternatives, mode selection) through 11 review sections to the summary, with explicit checkpoints ('Do NOT proceed without approval', the anti-skip rule, one-issue-at-a-time, commitment after mode selection, DONE/DONE_WITH_CONCERNS/BLOCKED statuses). Not a destructive or batch skill, so no cap applies; the residual gap is that the mode-selection gate depends on user approval but review-section flow has no equivalent verify step.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a single well-organized file with clear section headers and an unambiguous flow; nothing is buried or nested. The 18-pattern catalog and the 11-section detail could plausibly live in reference files to slim the always-loaded body, which is the main organization gap.

4 / 5

Total

15

/

20

Passed

Description

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

A strong trigger-focused description with excellent natural-language phrasing and a clear niche. Its main weakness is that the 'what' — what the skill actually does or outputs — is never stated independently, only implied through the list of user requests.

DimensionReasoningScore

Specificity

Names the plan-review domain with several concrete action verbs ('review a plan', 'challenge a proposal', 'poke holes in an approach', 'decide whether to expand or reduce'), but every action is framed as a user-request trigger rather than a statement of what the skill does or produces, so coverage of actual capabilities is implied rather than comprehensive.

3 / 5

Completeness

An explicit 'Use when asked to...' clause with concrete triggers clearly answers 'when', and the 'what' is present but only embedded inside the trigger verbs; a separate statement of what the skill does (e.g., produces a structured review with scope recommendations) would make both fully explicit.

4 / 5

Trigger Term Quality

Comprehensive coverage of natural phrases a user would actually say — 'review a plan', 'challenge a proposal', 'run a CEO review', 'poke holes in an approach', 'think bigger about scope' — with good synonym variation spanning critique, ambition, and scope-decision framings.

5 / 5

Distinctiveness Conflict Risk

The 'CEO review' / 'poke holes' / 'expand or reduce' framing carves out a distinct plan-review niche with minimal conflict risk, though generic terms like 'review' leave minor overlap with code-review or general review skills.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
garrytan/gstack
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.