SKILLEMALL.ai

BF create-llms

Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/

github/awesome-copilot Agent Skills author: github MIT 1 file body ≈ 1 781 tokens Open the sourcegithub.com analyzed 31 h ago

Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/

As a process F 44/100 · Will not run — References files that are not bundled: relative-url, README.md, CONTRIBUTING.md

GeneratorAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
F
44/100
Will not run
References files that are not bundled: relative-url, README.md, CONTRIBUTING.md
Tools and files w 18
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 1 more place: RA-Skills

How to improve

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: relative-url
  • warning missing-ref reference to a missing file: README.md
  • warning missing-ref reference to a missing file: CONTRIBUTING.md
  • warning missing-ref reference to a missing file: CODE_OF_CONDUCT.md
  • warning missing-ref reference to a missing file: spec/technical-spec.md
  • warning missing-ref reference to a missing file: spec/api-spec.md
  • warning missing-ref reference to a missing file: examples/basic-usage.md
  • warning missing-ref reference to a missing file: examples/advanced-usage.md
  • warning missing-ref reference to a missing file: docs/setup.md
  • warning missing-ref reference to a missing file: docs/deployment.md
  • warning missing-ref reference to a missing file: docs/architecture.md
  • warning missing-ref reference to a missing file: docs/decisions.md

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: relative-url, README.md, CONTRIBUTING.md
  • 0Tools and files. 12 referenced file(s) missing: relative-url, README.md, CONTRIBUTING.md
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 85Steps. 84 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1781 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)
  • -215 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 127: enough signal without eating the budget
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 84 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

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