AA strategical-alignment
Strategical alignment analysis — detect where short-term optimization (profit, efficiency, convenience) is building long-term fragility, dead ends, or collapse. Uses the White Rock method internally. Works at any scale: personal decisions, relationships, business strategy, technology trends, geopolitical moves, civilizational trajectories. Use this skill ONLY when the user explicitly asks for a structured long-term viability assessment of a named actor, organization, or system, AND the question describes a pattern of decisions or behaviors over time (not a single event), AND the time horizon is months or longer, AND the question warrants a multi-paragraph analytical response rather than a quick answer. DO NOT invoke for casual uses of the words 'sustainable', 'long-term', 'trap', or 'second-order' in ordinary conversation, single-event decisions, quick advice, or questions answerable in under 200 words. If in doubt, ask the user whether they want a full White Rock analysis before invoking.
As a process A 80/100 · Runs to the end — weak spots: execution cost, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 24696 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 80/100
- 0Progress reporting. Says nothing while it works
- 10Execution cost. Instruction body is 24696 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 155 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 40 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1004: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 22 headings
- +3Step-by-step instructions: 155 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.