SKILLEMALL.ai
GitHub ↗ RU Sign in

AB sector-analyst

This skill should be used when analyzing sector rotation patterns and market cycle positioning. It fetches sector uptrend data from CSV (no API key required) and optionally accepts chart images for supplementary analysis. Use this skill when the user requests sector rotation analysis, cyclical vs defensive assessment, overbought/oversold identification, or market cycle phase estimation. All analysis and output are conducted in English.

tradermonty/claude-trading-skills Agent Skills author: tradermonty 7 files · 4 scripts body ≈ 2 136 tokens Open the sourcegithub.com↗ analyzed 5 d ago

This skill should be used when analyzing sector rotation patterns and market cycle positioning.

As a process B 66/100 · Nearly there — weak spots: failures and branches, running it twice, progress reporting

AnalyzerMarketingData and analyticstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
99
Quality 40%
94
Run on models
none yet
Process rating
B
66/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
Running it twice w 4
30
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Secrets in code secret-high-entropy-token scripts/tests/test_analyze_sector_rotation.py:49
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
      def test…umn(self):
      fixture

    Files scanned: 7. 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 66/100

    • 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
    • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 71 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2136 tokens
    • low 11 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 439: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 71 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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