Interview Coach

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/interview-coach

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Interview Coach

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: What It Covers, Source, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when starting a job search and need a structured system
• Use when preparing for a specific interview (company research, mock, hype)
• Use when you want to analyze a past interview transcript
• Use when negotiating an offer or handling comp questions on recruiter screens
• Use when building or maintaining a storybank of interview-ready stories
• Use when the request clearly matches the imported source intent: Full job search coaching system — JD decoding, resume, storybank, mock interviews, transcript analysis, comp negotiation. 23 commands, persistent state.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. bash npx skills add dbhat93/job-search-os Then type /coach → kickoff.
2. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
3. Read the overview and provenance files before loading any copied upstream support files.
4. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
5. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
6. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
7. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.

Imported Workflow Notes

Imported: Install

npx skills add dbhat93/job-search-os

Then type

/coach

kickoff

Imported: Overview

A persistent, adaptive coaching system for the full job search lifecycle. Not a question bank — an opinionated system that tracks your patterns, scores your answers, and gets sharper the more you use it. State persists in

coaching_state.md

Imported: What It Covers

• JD decoding — six lenses, fit verdict, recruiter questions to ask
• Resume + LinkedIn — ATS audit, bullet rewrites, platform-native optimization
• Mock interviews — behavioral, system design, case, panel, technical formats
• Transcript analysis — paste from Otter/Zoom/Grain, auto-detected format
• Storybank — STAR stories with earned secrets, retrieval drills, portfolio optimization
• Comp + negotiation — pre-offer scripting, offer analysis, exact negotiation scripts
• 23 total commands across the full search lifecycle

Examples

Example 1: Ask for the upstream workflow directly

Use @interview-coach-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @interview-coach-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @interview-coach-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @interview-coach-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Example 1: Start your job search

/coach
kickoff

The coach asks for your resume, target role, and timeline — then builds your profile and gives you a prioritized action plan.

Example 2: Prep for a specific company

/coach
prep Stripe Senior PM

Runs company research, generates a role-specific prep brief, and queues up mock interview questions tailored to Stripe's process.

Example 3: Analyze an interview transcript

/coach
analyze

Paste a raw transcript from Otter, Zoom, or any tool. The coach auto-detects the format, scores each answer across five dimensions, and gives you a drill plan targeting your specific gaps.

Example 4: Handle a comp question

/coach
salary

Coaches you through the recruiter screen "what are your salary expectations?" moment with a defensible range and exact scripts.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/interview-coach

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @hugging-face-vision-trainer-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @humanize-chinese-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @hybrid-cloud-architect-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @hybrid-cloud-networking-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Source

https://github.com/dbhat93/job-search-os

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.