ClawHub

Resume Writing

v1.0.0

Deep resume workflow—target role, positioning statement, impact bullets with metrics, keyword alignment, ATS hygiene, and proofreading. Use when rewriting te...

⭐ 0· 137·0 current·0 all-time
by@mike47512

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mike47512/resume-writing.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Resume Writing" (mike47512/resume-writing) from ClawHub.
Skill page: https://clawhub.ai/mike47512/resume-writing
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install resume-writing

ClawHub CLI

Package manager switcher

npx clawhub@latest install resume-writing
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name, description, and content all describe a resume-focused, six-stage editing workflow. There are no unrelated requirements (no env vars, binaries, or installs) that conflict with the stated purpose.
✓
Instruction Scope
SKILL.md contains only guidance for structuring and editing resumes (targeting, bullets, ATS, proofreading). It does not instruct the agent to read system files, access environment variables, call external endpoints, or transmit data to unexpected destinations. The only implicit action is that the agent will need the user's resume text or job descriptions to apply the workflow—this is expected and proportional.
✓
Install Mechanism
No install spec and no code files; instruction-only skills are lowest-risk because nothing is written to disk or downloaded.
✓
Credentials
No credentials, config paths, or environment variables are requested. The workflow's needs (job descriptions, resume content) align with the stated purpose and don't require secret access.
✓
Persistence & Privilege
always is false and the skill does not request persistent or elevated privileges. It does not modify other skills or system-wide settings.
Assessment
This skill appears safe and coherent for editing resumes. Before using it, be prepared to provide the resume text and target job descriptions (these are needed for tailoring). Do not paste sensitive personal identifiers (SSNs, financial account numbers) into the resume text you share. Also verify any suggested metrics or numbers—the guidance correctly warns against fabrication; keep figures truthful and defensible in interviews.

Like a lobster shell, security has layers — review code before you run it.

latestvk970zjsnnc9m0b8rehhss6d3f183htbg
137downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0
@mike47512
latest
Download

Resume Writing (Deep Workflow)

A strong tech resume proves impact with evidence, not adjectives. Optimize for skimmability (recruiters spend seconds) and interview-defensible depth.

When to Offer This Workflow

Trigger conditions:

  • Active job search; career pivot (IC ↔ management, domain change)
  • Low response rate; resume too long or generic

Initial offer:

Use six stages: (1) target & positioning, (2) experience structure, (3) impact bullets, (4) skills & keywords, (5) ATS & format, (6) review & tailoring). Confirm regional norms (one page vs two for mid/senior).

Stage 1: Target & Positioning

Goal: One-line headline aligned with the next role you want—not every past title.

Exit condition: 2–3 target job descriptions saved as references for keyword alignment (without copying dishonestly).

Stage 2: Experience Structure

Goal: Reverse chronological; roughly 3–5 bullets per role; most recent role deepest.

Practices

  • Projects section only for early career, OSS, or notable side work

Stage 3: Impact Bullets

Goal: Pattern: strong verb + scope + quantified outcome (“Reduced p95 API latency 40% by…”).

Practices

  • Metrics: users, revenue, %, incidents avoided, time saved
  • Never fabricate numbers—approximate ranges only if ethically OK

Stage 4: Skills & Keywords

Goal: Skills section mirrors target JD language for tools you can defend in interview.

Stage 5: ATS & Format

Goal: Simple layout; standard headings; avoid critical text only inside images; PDF unless employer specifies otherwise.

Stage 6: Review & Tailoring

Goal: Tailor top bullets per application; proofread; peer review for clarity and exaggeration checks.

Final Review Checklist

  • Headline matches target role
  • Bullets emphasize measurable impact
  • Skills honest and interview-defensible
  • ATS-friendly formatting
  • Proofread; consistent tense and date format

Tips for Effective Guidance

  • Remove filler (“team player”) unless proven by story elsewhere.
  • Staff+ candidates: emphasize scope, multi-team leadership, and business outcomes.
  • Link GitHub/portfolio only if maintained and impressive.

Handling Deviations

  • Non-traditional path: emphasize projects with outcomes and certifications if relevant.

Comments

Loading comments...