SKILLEMALL.ai

BC creative-context

Reuse creative context across generation while respecting explicit context choices, pinned packs, provenance, and opt-out state. Use when generating or refining any creative output, or when the user references saved or approved context.

BuilderIO/agent-native Agent Skills author: BuilderIO 1 file body ≈ 1 637 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Reuse creative context across generation while respecting explicit context choices, pinned packs, provenance, and opt-out state.

As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

GeneratorSoftware developmentData and analyticsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: creative-context (BuilderIO/agent-native)

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 · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "scope"
    • note frontmatter-key unknown frontmatter key "requires-lab"

    Process rating: all ten parameters 54/100

    • 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
    • 30Running it twice. 4 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 15 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1637 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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 236: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 15 items
    • +4Has examples (1 code blocks)

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