strategist

Technical strategy and decision-making expert

Quality

59%

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/strategist/SKILL.md

Quality

Content

76%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 a lean, action-oriented set of decision templates that are copy-paste ready, but it presents examples rather than an explicit workflow with validation checkpoints, and all material is inlined in SKILL.md with no reference files.

Suggestions

Add a brief explicit workflow ('1. Gather context, 2. Enumerate options, 3. Score each, 4. Decide and record rationale, 5. Validate against success metrics') so Claude follows a repeatable sequence.

Include a validation/verification checkpoint such as 'Re-check that success metrics are measurable and that every option was scored on the same criteria before finalizing the decision.'

Move the three full templates into separate reference files (e.g. references/technology-selection.md) and keep SKILL.md as an overview with one-level-deep links to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely structured example templates with no padded explanations of what React, Auth0, or microservices are, fitting 'Efficient; minor instances of over-explanation that could be trimmed'; the closing Sun Tzu quote is the only non-essential padding, keeping it below 5.	4 / 5
Actionability	It provides copy-paste-ready markdown templates with scored options, cost/ROI figures, and risk grids that cover the common decision cases, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The templates imply a sequence (Context -> Options -> Decision -> Rationale -> Trade-offs -> Success Metrics) but there is no explicit step ordering for Claude to follow and no validation/verification checkpoints, matching 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Decision Framework, Strategic Planning, Risk Assessment) with no nested references, matching 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'; it loses the final point because the full templates are inlined rather than split into reference files.	4 / 5
	Total	16 / 20 Passed

Description

25%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 a terse role label that identifies the domain but provides no concrete capabilities, no natural trigger terms, and no usage guidance, making it likely to be passed over or conflict with adjacent skills.

Suggestions

Add concrete actions, e.g. 'Compares technology options, runs build-vs-buy analysis, and documents risk/trade-off decisions using structured templates.'

Append a 'Use when...' clause with natural triggers such as 'Use when choosing between frameworks or libraries, deciding build vs buy, or planning a migration with risk trade-offs.'

Include synonyms users actually say ('should we build or buy', 'compare options', 'decision matrix') to improve trigger matching and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'Technical strategy and decision-making expert' names the domain but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it is a role label, not a capability list, so it does not reach 3.	2 / 5
Completeness	It gives only a vague 'what' (an expert role) and has no 'when'/'Use when' clause; per the guidelines a missing trigger clause caps completeness at 3, and this is below that at 'vague what and no when'.	2 / 5
Trigger Term Quality	Only 'strategy' and 'decision-making' appear, which are generic labels rather than the natural phrases a user would utter ('should we use React or Vue', 'build vs buy'); this matches 'One or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	'Technical strategy and decision-making expert' is very broad and would overlap with architecture, planning, or general advising skills, matching 'Very broad; high overlap risk with many similar skills'.	2 / 5
	Total	8 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TurnaboutHero/oh-my-antigravity
Path: skills/strategist/SKILL.md
Commit: f73e1ff

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