SKILLEMALL.ai
GitHub ↗ RU Sign in

CC crossframe-review

Use when explicit CrossFrame output needs review for reasoning fidelity, evidence boundaries, source anchors, concept drift, article collapse, or repair steps.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 13 files body ≈ 1 372 tokens Open the sourcegithub.com↗ analyzed 5 d ago

This skill depends on sibling crossframe and, for article workflows, crossframe-essay/crossframe-suite resources.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

AnalyzerQuality controltype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 12. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 159 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "license_source"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 57/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 50When it triggers. No condition that starts the skill
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 67 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1372 tokens
  • 100Running it twice. No mutating operations
  • 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
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -44 reference files, but SKILL.md never points to them: the model will not open them
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 159: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 67 items
  • +1License stated

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