# Extract Interview STAR Stories

Completed work is hard to turn into clear interview answers. This skill structures achievements as concise STAR stories with technical depth.

## Install

```bash
npx skillstore add danielpodolsky/star-story-extraction
```

## Metadata

- Status: approved
- Slug: danielpodolsky-star-story-extraction
- Skillstore revision: r1
- Version status: missing
- Tree hash: 39c811c66d11e6a1d6ffff7d374f92c2e7dc221f9b544d53d7a9cfa263ee2413
- Author: DanielPodolsky
- GitHub username: DanielPodolsky
- License: MIT
- Repository: https://github.com/DanielPodolsky/mentor-spec/tree/main/.claude/skills/career/star-stories
- Ref: 34f316ba14ef36c7a620fc09f2676d2429997a77
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/danielpodolsky-star-story-extraction
- Manifest: https://skillstore.pages.dev/api/skills/danielpodolsky-star-story-extraction/manifest

## Capabilities

- Identifies the story type for completed technical work.
- Guides users through situation, task, action, and result prompts.
- Provides a reusable Markdown story template.
- Shows examples of weak and strong STAR answers.
- Suggests interview question variations for each story.
- Recommends saving stories under a career stories folder.

## Use Cases

- Prepare Behavioral Answers: Turn a finished project into a focused story for behavioral interviews.
- Capture Work Wins: Record achievements soon after delivery, while details and metrics are still fresh.
- Coach Junior Developers: Use guided questions to help juniors describe ownership, decisions, and results.

## Prompt Templates

### Create a Basic STAR Story

```
Use this completed task: [task]. Ask me for missing context, then draft a STAR story.
```

### Improve Story Depth

```
Review this draft STAR story: [story]. Strengthen technical actions, ownership, and measurable results.
```

### Map Story to Questions

```
Given this STAR story: [story]. List interview questions it can answer and adapt the wording for each.
```

### Build a Story Portfolio

```
Review these project notes: [notes]. Extract three distinct STAR stories and label the strongest interview theme for each.
```

## Limitations

- It does not verify whether metrics are accurate.
- It depends on user-provided project context.
- It does not conduct live interview practice.
- It does not create resumes or cover letters.

## Best Practices

- Capture metrics and dates while the project details are fresh.
- Use first-person language for actions you personally owned.
- Keep each spoken story near two to three minutes.

## Anti Patterns

- Do not invent metrics or claim outcomes you cannot support.
- Do not describe only team work without your specific decisions.
- Do not include long background that hides the main technical action.

## Security Audit

- Audited at: 2026-07-06T09:53:34.539\+00:00
- Summary: All static command-execution hits are Markdown code fence delimiters or template prose, not executable instructions. The reconnaissance hits are ordinary interview-writing prompts and do not request system inspection or data collection. No semantic prompt injection or exfiltration intent was found.

## Stats

- Views: 206
- Downloads: 11
- Favorites: 0
- Popularity score: 0