SKILLEMALL.ai

CF linear

Read and manage software issues, tickets, projects, and planning data in Linear. Use to review sprints and cycles, identify ticket rollover and release blockers, and update issue status, assignees, priorities, and milestones through Linear's official MCP server.

asgeirtj/system_prompts_leaks Agent Skills author: asgeirtj CC0-1.0 3 files body ≈ 562 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Read and manage software issues, tickets, projects, and planning data in Linear.

As a process F 23/100 · No process to follow — References files that are not bundled: <scope_add_url>

AnalyzerAI and agentsOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
F
23/100
No process to follow
References files that are not bundled: <scope_add_url>
Tools and files w 18
0
Steps w 15
0
Result and completion w 14
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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 missing-ref reference to a missing file: <scope_add_url>
  • note frontmatter-key unknown frontmatter key "icon"

Process rating: all ten parameters 23/100

Will not run. References files that are not bundled: <scope_add_url>
  • 0Tools and files. 1 referenced file(s) missing: <scope_add_url>
  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 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
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 562 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)
  • +4Structure: 1 headings, hard to scan
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 262: enough signal without eating the budget
  • +4Has examples (1 code blocks)

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