outcome

Record job application results in a tracker CSV and per-application archive folders.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/zaheer037/job-search --skill outcome-zaheer037
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: outcome
Source: https://github.com/zaheer037/job-search/tree/main/.agents/skills/outcome
Command: npx skills add https://github.com/zaheer037/job-search --skill outcome-zaheer037

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Job seekers lose track of what happened to each application: which ones got interviews, which went silent, and which deserve a follow-up. This Skill systematically records application outcomes so the rest of the job-search workflow (ranking, calibration, interview prep) has accurate data to work from. ## Core Features & Use Cases - Outcome Recording: Logs progress updates (interviews, offers) and final resolutions (hired, rejected, no_response) into job_search_tracker.csv and a per-application outcome.md archive. - Follow-Up Branch: Surfaces applications quiet for 10+ days, drafts a brief follow-up note in your voice based only on submitted materials, and logs it with a dated marker. - Stale Sweep: Batch-resolves applications quiet for 60+ days as no_response, but only after explicit user confirmation. - Use Case: After a recruiter calls with a rejection, run /outcome acme to update the tracker, archive the submitted CV and cover letter, and get a suggestion to calibrate your evaluation framework once enough outcomes accumulate. ## Quick Start Ask the agent to run /outcome followed by a company name to record what happened with that application.

Frequently Asked Questions about outcome

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track job application statuses in a CSV file?▼

Run /outcome with a company name to update the row's status column using canonical values like applied, interview, offer, hired, rejected, or no_response. The command appends a dated note without commas or line breaks so the CSV structure stays intact.

How to follow up on a job application with no response?▼

Run /outcome followup to list applications quiet for 10 or more days with fewer than two follow-ups sent. The skill drafts a 60-120 word note based only on your submitted materials, which you review and send yourself.

Can I batch-close old job applications that never replied?▼

Yes, run /outcome stale or /outcome sweep to list open applications quiet for 60+ days. You confirm with all, select, or skip before anything is written; qualifying rows are marked no_response in both the tracker and archive.

Does the outcome command send follow-up emails automatically?▼

No, the follow-up branch only drafts text for you to send yourself. It never emails, messages, or submits anything, and it must not be wired to tools that do.

What happens when I record enough application outcomes?▼

Once three or more applications reach a final status, the skill suggests running /setup Path A, which calibrates fit scoring from what actually got interviews and mines your feedback for STAR examples. The outcome command itself never edits framework files.