Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →okhp3/okhp3-askjamie-style-registry
OverKill Hill P³ visual style registry and application workflow.
Passed 17 of 22 test cases with the skill, and 7 of 22 without it.
and 13 more in the full report
10 fixed7 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
A user provides three URLs from different brand sub-domains (`shop.acme.com`, `docs.acme.com`, and `acme-careers.com`). What must be confirmed with the user before combining evidence into a single profile file?
| Checked | Without skill | With skill |
|---|---|---|
| Confirms single-identity ownership with the user before combining multiple sources | Passed | Passed |
| Requires creating separate profiles when sources represent distinct visual identities | Missed | Passed |
The instructions your model reads when the skill loads.
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Build a durable library of named visual profiles, then use it to create work that feels intentionally aligned instead of generically themed. Treat a profile as design evidence and reusable direction, not as permission to copy another organization’s identity.
This skill has two operating modes: capture a source into a named profile, or apply one or more existing profiles to a target. Keep those modes separate. A capture updates the library only after provenance and confidence are recorded; an application changes the target only after the profile roles and target boundaries are explicit.
Before applying this workflow, read references/brand-overlay.md. The overlay adds AskJamie source routing, visual vocabulary, and application boundaries; it does not override provenance, privacy, evidence, or approval gates.
| In scope | Out of scope |
|---|---|
| Websites, CSS, visual documents, presentations, infographics, and image assets | Logo recreation, trademark clearance, or identity theft |
| SPA styling, documentation direction, presentation direction, and image briefs | Applying styles with no target owner approval |
| One primary style with carefully bounded supporting styles | Silent palette, type, or layout averaging |
Store each style in its own profile file and list it in a registry. There is no fixed profile limit. The separation preserves provenance, makes profiles independently reusable, and prevents a later capture from overwriting an established identity.
Use this layout unless the target repository already has a stronger convention:
brand-styles/
registry.yaml
profiles/
<style-id>.yaml
If the target repository already has a style-library convention, preserve it and map the same profile fields into that convention. Do not create a second registry merely because the directory name differs.
At capture time, ask the user for a human-readable style name and a stable slug. If the user provides several sources for one identity, confirm that they belong to one profile before combining their evidence. If sources represent different identities, create separate profiles.
test cases passed, vs 7 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.