skills/creative-portfolio-resume/SKILL.md
This skill should be used when the user needs to balance visual design with ATS compatibility for a creative role resume. Use when building portfolio resumes for design, marketing, writing, or other creative fields, and when deciding between a designed version versus an ATS-safe version.
npx skillsauth add ericgandrade/claude-superskills creative-portfolio-resumeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The Problem:
The Solution: Two-version approach:
Even the ATS version can show creativity through:
1. Show, Don't Just Tell
2. Clarity Over Cleverness
3. Brand Consistency
Typography:
Color:
Layout:
Visual Accents:
Must Show:
Resume Approach:
Must Show:
Resume Approach:
Must Show:
Resume Approach:
Must Show:
Resume Approach:
Must Show:
Resume Approach:
Link to Portfolio:
Portfolio: yourname.com
Link to Specific Work:
• Redesigned checkout flow, increasing conversion by 40%
Case Study: yourname.com/checkout
Options:
Best Practice:
Design Software:
Simpler Options:
Avoid:
Display progress before each creative resume phase:
[████░░░░░░░░░░░░░░░░] 25% — Phase 1/4: Assessing Creative Field & Target Role
[████████░░░░░░░░░░░░] 50% — Phase 2/4: Defining Design Strategy (ATS vs. Designed)
[████████████░░░░░░░░] 75% — Phase 3/4: Creating Content for Both Versions
[████████████████████] 100% — Phase 4/4: Delivering Creative Resume Strategy
When creating a creative resume:
# CREATIVE RESUME STRATEGY
## Role Type: [Design/Marketing/Creative]
## Industry: [Agency/In-house/Freelance]
## Version Strategy
### Version 1: ATS-Compatible
**Use for:** Online applications, job boards
**Format:** .docx and .pdf
**Design level:** Clean and professional, minimal embellishment
### Version 2: Designed
**Use for:** Portfolio, networking, direct outreach
**Format:** .pdf (print-quality)
**Design level:** Full creative treatment
## Design Specifications
### Typography
- Headline: [Font name, weight, size]
- Body: [Font name, weight, size]
- Accent: [Font name, use case]
### Colors
- Primary: [Hex code] - [Use case]
- Secondary: [Hex code] - [Use case]
- Text: [Hex code]
### Layout
- Format: [Single column / Two column]
- Margins: [Specifications]
- Grid: [If applicable]
## Portfolio Integration
- Main portfolio link: [URL]
- Case studies to highlight: [List]
- Resume page on portfolio: [Y/N]
## Content Adjustments for Creative Field
- [Specific content recommendation]
- [Specific content recommendation]
testing
This skill should be used when the user needs to create, validate, standardize, or repair YAML frontmatter properties in Obsidian notes. Use when the user wants to add or update tags, aliases, dates, custom properties, or any metadata fields in the Properties panel of an Obsidian note.
development
This skill should be used when the user needs to create or edit an Obsidian Canvas — a freeform visual workspace that arranges notes, cards, links, images, and web content on an infinite canvas. Use when the user wants to map ideas spatially, build a knowledge dashboard, sketch a concept cluster, or create a visual workspace linking multiple Obsidian notes.
tools
This skill should be used when the user wants to automate repetitive Obsidian tasks using the Obsidian CLI, shell commands, or scripted workflows. Use when the user needs to batch-create notes, bulk-update frontmatter, run vault maintenance tasks, open specific notes in Obsidian, navigate the vault programmatically, or integrate Obsidian with external tools.
development
This skill should be used when the user needs to create, edit, or convert a diagram into Mermaid syntax. Use when the user asks for a flowchart, sequence diagram, class diagram, state diagram, entity-relationship diagram, mindmap, Gantt chart, or any other diagram type that Mermaid supports. Outputs a ready-to-render Mermaid code block.