Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsGraphic Callout Brief
Converts proposal prose into technical graphic briefs for illustrators, mapping art to scorable requirements.
$19
Graphic Callout Brief
Example session with this skill installed
From section 3.2 (Identity Management), generate up to 2 graphic briefs. Use the provided sow_items [ID-04, ID-09] and assume a 0.25 page budget per figure. No proof points provided.
- Read your context and instructions
- Compiled the graphic callout brief
- Generated the UI component
I have analyzed section 3.2 regarding Identity Management. From the inventory of mechanisms and requirements, I have developed two graphic briefs focused on the authentication flow and the authorization boundary. A third candidate (Company Excellence) was dropped as it was a slogan without a scorable mechanism.
Brief 1. Multi-Factor Authentication Flow
- kind: flow
- section_id: 3.2
- sow_id: ID-04
- page_share: 0.25
- claim: The system enforces MFA via a central identity provider before granting session tokens.
- actors: End User, IAM Administrator
- systems: Identity Provider (IdP), Access Broker, Token Service
- labels: Login Request, Challenge/Response, Validation, Token Issuance, Encrypted Session
- sequence: User -> IdP (Challenge); User -> IdP (Response); IdP -> Token Service (Success); Token Service -> User (Session)
- do_not_illustrate:
- Corporate logos
- Real-world maps
- Biometric clip-art (fingerprints/eyes)
- caption: Figure 3.2-1. The integrated IAM workflow ensures MFA validation prior to session establishment.
- source_block: Para_02
Brief 2. Access Control Boundary
- kind: boundary
- section_id: 3.2
- sow_id: ID-09
- page_share: 0.25
- claim: Role-based access controls separate administrative functions from standard user operations.
- actors: Standard User, Privileged Admin, Auditor
- systems: Production Environment, Management Plane
- labels: Read-Only Access, Full Control, Audit Logs, RBAC Filter
- sequence: n/a
- do_not_illustrate:
- Padlock icons
- Specific vendor cloud logos (AWS/Azure)
- Named customer personnel
- caption: Figure 3.2-2. Defined boundaries ensure administrative isolation and auditability.
- source_block: Table_01
Dropped Candidates
| Candidate | Kind | Action | Reason |
|---|---|---|---|
| Decades of Trust | slogan | dropped | no shall / decorative only |
Next steps
- Hand these briefs to the graphic design team for layout in the proposal template.
- Verify that the "do-not-illustrate" items are excluded from the first drafts.
- Insert the final figure numbers into the section 3.2 prose references.
graphic-callout-brief.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Graphic artists and illustrators often lack the domain context of a specific proposal section, leading to decorative "fluff" rather than scorable technical art. Conversely, subject matter experts often fail to provide enough detail for a designer to create accurate diagrams without reading the entire proposal.
What it does
- Analyzes a single written proposal section to inventory technical claims, mechanisms, and metrics.
- Ranks potential graphics based on their ability to help evaluators score the section.
- Generates 1 to 3 detailed briefs for illustrators, including specific claims, actor labels, and sequence steps.
- Enforces strict "do-not-illustrate" constraints to prevent hallucinated logos, slogans, or unproven metrics.
Why this beats prompting it yourself
General prompts often produce generic descriptions or try to generate low-quality AI images. This skill follows a rigorous proposal methodology that separates technical mechanisms from decorative slogans, ensuring every graphic brief maps directly to a solicitation requirement (SOW/PWS) without inventing new mandates.
Use cases
- Extracting a technical flow diagram from a complex narrative process description.
- Creating a "boundary" brief that defines roles and permissions for a security section.
- Briefing a callout graphic for a specific scorable claim that prose alone cannot carry.
- Identifying and rejecting "decorative" graphic requests that don't add evaluative value.
Known limitations
This skill produces written briefs only. It does not generate images, SVG code, or slide masters. It requires a completed section draft and will not function on blank pages or disjointed drafts.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 1 day ago
- Passed all security checks, Safe to install