brand-spec-extraction skillA
brand-spec-extraction is agent-read markdown (skill) from jnpiyush/agentx: Extract and codify a brand specification from user-provided sources (URL, screenshot, PDF, existing app) into a deterministic brand-spec.md artifact. Captures palette, typography, voice, motion, and prohibited patterns so downstream design decisions can be defended against the real brand instead of invented from scratch..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
<!-- Source: 5-step brand-spec extraction protocol adapted from alchaincyf/huashu-design's "locate, screenshot, grep, codify, vocalise" flow, via nexu-io/open-design (Apache-2.0). See repository NOTICE. --> # Brand Spec Extraction > WHEN: A user references an existing brand (URL, screenshot, deck, PDF, > app, or "match the look of X"). Run BEFORE picking a visual direction or > writing any prototype CSS. The output is a single artifact at > `docs/ux/brand-spec-<issue>.md` that every subsequent design step cites. A design choice that contradicts the extracted brand-spec must be flagged as a finding, not silently overridden. The spec is the source of truth. ## When to Use This Skill - User says "make it match our website at example.com" - User attaches a screenshot, deck, PDF, or Figma export of an existing brand - The product is an extension of an existing app with established UI - An issue carries `needs:brand-fidelity` ## The 5-Step Protocol ### Step 1 - Locate the source Identify exactly what authoritative artifact the brand lives in. Order of preference: 1. Live website at a stable URL. 2. Brand-guidelines PDF or deck. 3. Existing app screenshots. …
Read the whole file at its exact version.
How to install
mdr add jnpiyush/agentx/brand-spec-extraction@v1.0.0mdr add jnpiyush/agentx/brand-spec-extraction@sha256:78a2f9feaa2312abPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_wzt7z4i5lu5m3tvb)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-15 | f17c505 | 7,645 B | A | view · diff |
| v1.0.0 | 2026-05-17 | 4703a79 | 7,643 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7645 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jnpiyush/agentx · 16 stars · license Apache-2.0 · pushed 2026-09-21 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_wzt7z4i5lu5m3tvb GET https://markdownregistry.com/api/v1/resolve?ref=jnpiyush/agentx/brand-spec-extraction GET https://markdownregistry.com/api/v1/blob/78a2f9feaa2312abab08e9486d5aebe5993b978777baba4c13f39cfc60150196
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.