SKILLEMALL.ai
GitHub ↗ RU Sign in

AC sector-analyst

This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns. Use this skill when the user provides performance chart images (1-week or 1-month timeframes) for sectors or industries and requests market cycle assessment, sector rotation analysis, or strategic positioning recommendations based on performance data. All analysis and output are conducted in English.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 2 019 tokens Open the sourcegithub.com↗ analyzed 2 d ago

This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns.

As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice

AnalyzerMarketingtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
C
63/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 63/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 85Steps. 60 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2019 tokens

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 433: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 60 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.