update

Update tracked job application statuses across pipeline stages with notes.

2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/alwaysmap/jobs4me --skill update-alwaysmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/alwaysmap/jobs4me/tree/main/skills/update
Command: npx skills add https://github.com/alwaysmap/jobs4me --skill update-alwaysmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill when the user wants to update a role's status, move a role through pipeline stages, decline a role, mark something as applied or interviewing, or report a rejection. Triggers on "update", "applied to", "got rejected", "decline", "not interested", "got an offer", "interviewing at", or any status change for a tracked role. Also use when the user just says /update with no arguments to show their active roles.

Core Features & Use Cases

  • Update and set the status of a tracked role across the pipeline (e.g., suggested, maybe, applied, interview, offered, rejected, closed).
  • Parse user input with support for common shorthand and optional notes, auto-attach notes with timestamps, and locate the correct role by company when multiple exist.
  • After a change, update the Kanban board, provide context-driven guidance (e.g., suggest /prep for interviewing, /apply for offers), and support special flows like offer evaluation.

Quick Start

Use the update skill to move a role through your pipeline by typing '/update Acme - applied'.

Frequently Asked Questions about update

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

FAQPage Schema
How do I update my job application pipeline status when I get an interview or offer?

To update your job application pipeline status, you can type a command like '/update Acme - interviewing' to move a role through stages like applied, interviewing, offered, or rejected. The skill parses natural shorthand input to automatically locate the correct role and update its status.

Can I add notes to a tracked job application when moving it to a new pipeline stage?

Yes, you can add notes when updating a job application status. The skill parses optional notes from your input, auto-attaches them with timestamps, and preserves existing notes during stage transitions to maintain a complete history of your interactions.

What happens if I run an update command with no arguments for my job tracker?

Running an update command with no arguments shows all your active roles currently tracked in the pipeline. This provides a quick overview of your job application statuses across stages like suggested, maybe, applied, interviewing, offered, rejected, and closed.

How does the job tracker handle status updates when I have multiple roles at the same company?

When multiple roles exist at the same company, the skill locates the correct role by parsing your input and company name. It ensures the status update applies to the intended job application without accidentally modifying other tracked positions.

Does the pipeline update skill provide guidance after I change a job application status?

After a status update, the skill provides context-driven guidance such as suggesting interview prep for interviewing roles or application steps for offers. It also updates the Kanban board and supports special flows like offer evaluation when relevant.

What's the best way to decline a job offer or mark a role as not interested in my pipeline?

To decline a job offer or mark a role as not interested, you can use triggers like 'decline', 'not interested', or 'got rejected'. The skill updates the pipeline status accordingly and moves the role to the rejected or closed stage on your Kanban board.