strategist

Technical strategy and decision-making expert

Quality

21%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides useful decision-making templates and examples but reads more like documentation than actionable instructions for Claude. The content is example-heavy without clear directives on when and how to apply each framework, and lacks the lean, instruction-focused approach that makes skills effective.

Suggestions

Add a concise 'When to use this skill' section at the top with clear triggers (e.g., 'Use this framework when user asks for technology recommendations or build-vs-buy analysis')

Convert verbose examples into condensed templates with placeholders, moving full examples to a separate EXAMPLES.md file

Add explicit workflow steps: '1. Identify decision type → 2. Gather context → 3. Apply relevant framework → 4. Present recommendation with trade-offs'

Remove the Sun Tzu quote and any decorative content that doesn't provide actionable guidance

Dimension	Reasoning	Score
Conciseness	The content is moderately efficient but includes verbose examples that could be condensed. The full decision framework examples are illustrative but lengthy, and the Sun Tzu quote adds no actionable value.	2 / 3
Actionability	Provides structured templates and examples for decision-making, but these are illustrative scenarios rather than executable guidance. Missing concrete instructions on how to actually apply these frameworks or what tools/commands to use.	2 / 3
Workflow Clarity	The examples show decision processes with clear sections (Context, Options, Decision, Trade-offs), but there's no explicit workflow for Claude to follow when making decisions. The phased approach in risk assessment is good but lacks validation checkpoints.	2 / 3
Progressive Disclosure	Content is a monolithic wall of examples with no references to external files or clear navigation structure. All content is inline with no indication of where to find more detailed guidance or related materials.	1 / 3
	Total	7 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is critically weak across all dimensions. It provides no concrete actions, no trigger terms, no usage guidance, and is so generic it would be impossible for Claude to reliably select this skill over others. It reads more like a vague job title than a functional skill description.

Suggestions

Define specific concrete actions this skill performs (e.g., 'Evaluates architecture trade-offs, compares technology options, creates decision matrices').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about technology choices, architecture decisions, or needs help weighing technical trade-offs').

Narrow the scope to a distinct niche to avoid conflicts with other skills (e.g., focus on 'software architecture decisions' rather than generic 'technical strategy').

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('technical strategy', 'decision-making expert') without naming any concrete actions or specific capabilities.	1 / 3
Completeness	Missing both 'what does this do' (no concrete actions) and 'when should Claude use it' (no trigger guidance or 'Use when...' clause).	1 / 3
Trigger Term Quality	Contains no natural keywords users would actually say when seeking help. 'Technical strategy' and 'decision-making' are overly generic and not tied to specific user requests.	1 / 3
Distinctiveness Conflict Risk	Extremely generic description that could conflict with virtually any skill involving technical work or decisions. No clear niche or distinct triggers.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 4 months 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.