SKILLEMALL.ai
GitHub ↗ RU Sign in

AC Named Immortal

Empowers AI agents with crypto resource vitality assessment. Calls the Majestify API (crypto-health-hub) to compute Sharpe, Sortino, VaR, CVaR, drawdown, and other risk metrics, then classifies assets as IMMORTAL, MORTAL, or CRITICAL. Zero local dependencies — works anywhere with internet access.

ClawHub Agent Skills author: Majesty Atenkhu v1.0.0 3 files body ≈ 643 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency

AnalyzerData and analyticsInfrastructureAI and agentstype 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
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
C
55/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 55/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (Named Immortal) differs from the folder (immortal)
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 12 steps
  • 100Execution cost. Instruction body is 643 tokens
  • 100Running it twice. No mutating operations

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)
  • +2Single-language instructions
  • +3Description length 297: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 12 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: clean
This skill is a disclosed crypto-risk lookup tool that contacts an external API and does not show hidden local access, persistence, credential use, or destructive behavior.
LLM: benign (high) · VirusTotal: suspicious · 27 May 2026