Resume Bullet Extraction

{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-01-16T23:31:19.530Z",
    "slug": "danielpodolsky-resume-bullet-extraction",
    "source_url": "https://github.com/DanielPodolsky/mentor-spec/tree/main/.claude/skills/career/resume-bullets",
    "source_ref": "main",
    "model": "claude",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "1359798624154f0174d9318fc1351083c04098bf0350d67732372e2bb45f1296",
    "tree_hash": "c6fd19e3e9ee619b08e164f8c53d49c345ad6743dd5240c7a7bc0c0114f93656"
  },
  "skill": {
    "name": "resume-bullet-extraction",
    "description": "Auto-invoke after task completion to generate powerful resume bullet points from completed work.",
    "summary": "Auto-invoke after task completion to generate powerful resume bullet points from completed work.",
    "icon": "📝",
    "version": "1.0.0",
    "author": "DanielPodolsky",
    "license": "MIT",
    "category": "career",
    "tags": [
      "resume",
      "career",
      "job search",
      "professional development"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "network",
      "filesystem",
      "external_commands"
    ]
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "summary": "Pure documentation skill containing only markdown templates and resume writing guidance. All static findings are false positives: hash strings misidentified as C2/weak crypto, markdown backticks misidentified as shell execution, and security-related vocabulary in resume examples misidentified as cryptographic code. No code execution, file access, network calls, or external commands.",
    "risk_factor_evidence": [
      {
        "factor": "network",
        "evidence": [
          {
            "file": "skill-report.json",
            "line_start": 6,
            "line_end": 6
          }
        ]
      },
      {
        "factor": "filesystem",
        "evidence": [
          {
            "file": "skill-report.json",
            "line_start": 6,
            "line_end": 6
          }
        ]
      },
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 18,
            "line_end": 20
          },
          {
            "file": "SKILL.md",
            "line_start": 20,
            "line_end": 97
          },
          {
            "file": "SKILL.md",
            "line_start": 97,
            "line_end": 103
          },
          {
            "file": "SKILL.md",
            "line_start": 103,
            "line_end": 106
          },
          {
            "file": "SKILL.md",
            "line_start": 106,
            "line_end": 112
          },
          {
            "file": "SKILL.md",
            "line_start": 112,
            "line_end": 115
          },
          {
            "file": "SKILL.md",
            "line_start": 115,
            "line_end": 121
          },
          {
            "file": "SKILL.md",
            "line_start": 121,
            "line_end": 124
          },
          {
            "file": "SKILL.md",
            "line_start": 124,
            "line_end": 130
          },
          {
            "file": "SKILL.md",
            "line_start": 130,
            "line_end": 149
          },
          {
            "file": "SKILL.md",
            "line_start": 149,
            "line_end": 158
          },
          {
            "file": "SKILL.md",
            "line_start": 158,
            "line_end": 161
          },
          {
            "file": "SKILL.md",
            "line_start": 161,
            "line_end": 167
          },
          {
            "file": "SKILL.md",
            "line_start": 167,
            "line_end": 219
          },
          {
            "file": "SKILL.md",
            "line_start": 219,
            "line_end": 221
          }
        ]
      }
    ],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 2,
    "total_lines": 395,
    "audit_model": "claude",
    "audited_at": "2026-01-16T23:31:19.530Z"
  },
  "content": {
    "user_title": "Generate Impactful Resume Bullets from Completed Work",
    "value_statement": "Software engineers struggle to translate technical work into compelling resume content. This skill transforms completed tasks into powerful, quantified resume bullet points using proven formulas.",
    "seo_keywords": [
      "resume bullet points",
      "resume writing",
      "career development",
      "job search",
      "professional resume",
      "Claude Code skill",
      "Claude skill",
      "Codex skill",
      "technical resume"
    ],
    "actual_capabilities": [
      "Generate resume bullets using action verb + accomplishment + technology + impact formula",
      "Quantify achievements with specific metrics and business impact",
      "Apply templates for feature implementation, performance optimization, bug fixes, and architecture decisions",
      "Identify the most impressive aspects of completed technical work"
    ],
    "limitations": [
      "Does not access or modify your actual resume files",
      "Does not integrate with external job platforms or application systems",
      "Does not provide career coaching beyond resume bullet writing",
      "Cannot verify information against job descriptions automatically"
    ],
    "use_cases": [
      {
        "target_user": "Software Engineers",
        "title": "Document Technical Impact",
        "description": "After completing a feature, instantly generate a polished resume bullet that highlights your contribution and technologies used."
      },
      {
        "target_user": "Engineering Managers",
        "title": "Track Team Accomplishments",
        "description": "Systematically capture project outcomes with quantifiable metrics for performance reviews and career advancement."
      },
      {
        "target_user": "Job Seekers",
        "title": "Update Application Materials",
        "description": "Transform any completed work item into a compelling bullet point that passes ATS systems and impresses technical interviewers."
      }
    ],
    "prompt_templates": [
      {
        "title": "Basic Feature",
        "scenario": "After building a feature",
        "prompt": "Generate a resume bullet for building a new feature using [technology] that [describe what it does]."
      },
      {
        "title": "Performance Work",
        "scenario": "After optimizing performance",
        "prompt": "Create a resume bullet for optimizing [component] by [method], resulting in [metric improvement]."
      },
      {
        "title": "Bug Resolution",
        "scenario": "After fixing a bug",
        "prompt": "Draft a resume bullet for resolving [problem] through [solution], preventing [impact]."
      },
      {
        "title": "Complete Story",
        "scenario": "After significant project",
        "prompt": "Extract all significant resume bullets from this completed work [paste work summary], focusing on technical depth and quantifiable impact."
      }
    ],
    "output_examples": [
      {
        "input": "I just finished implementing a new authentication system with JWT tokens and refresh token rotation using Node.js and Redis. It handles 50,000 daily users and eliminated all session hijacking vulnerabilities.",
        "output": [
          "Engineered JWT authentication with refresh token rotation using Node.js and Redis, eliminating session hijacking vulnerabilities and supporting 50,000+ daily active users",
          "Architected secure authentication system reducing vulnerability surface by implementing token refresh mechanics and Redis-based session storage"
        ]
      }
    ],
    "best_practices": [
      "Always quantify impact with specific numbers, percentages, or scale metrics",
      "Include specific technologies and technical context in every bullet",
      "Start with strong action verbs that demonstrate ownership and initiative"
    ],
    "anti_patterns": [
      "Using passive language like 'Responsible for' or 'Helped with'",
      "Writing generic bullets without specific technologies or metrics",
      "Including jargon that non-technical recruiters cannot understand"
    ],
    "faq": [
      {
        "question": "Which AI tools support this skill?",
        "answer": "Compatible with Claude, Codex, and Claude Code. Works across all conversation contexts."
      },
      {
        "question": "What makes a strong resume bullet?",
        "answer": "Strong bullets use action verbs, specific technologies, quantifiable impact, and demonstrate ownership of outcomes."
      },
      {
        "question": "How do I integrate this into my workflow?",
        "answer": "Auto-invoke after task completion. Paste your work summary and receive polished bullets ready for your resume."
      },
      {
        "question": "Is my data safe?",
        "answer": "This is a prompt-based skill with no file access or data collection. All processing happens within your AI conversation."
      },
      {
        "question": "Why are my bullets coming out vague?",
        "answer": "Provide more specific details about technologies used, scale achieved, and measurable outcomes from your work."
      },
      {
        "question": "How is this different from other resume tools?",
        "answer": "This skill focuses on technical impact quantification specifically for engineers, using proven STAR methodology."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 224
    }
  ]
}