Skip to content
Skills Library
Personal productivity · Planning

tracking

/tracking

Record or look up my tracking (applications, follow-ups, interviews, answers, rejections, offers I found myself, notes). Use when the request starts with "Tracking", when I tell you what I did on my side, or when I ask where I stand with a company.

Author
dweuk ↗
Licence
MIT
Last repository change
30.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Record or look up my tracking (applications, follow-ups, interviews, answers, rejections, offers I found myself, notes). Use when the request starts with "Tracking", when I tell you what I did on my side, or when I ask where I stand with a company.

Triggers from the description

Tracking
Original author description

Record or look up my tracking (applications, follow-ups, interviews, answers, rejections, offers I found myself, notes). Use when the request starts with "Tracking", when I tell you what I did on my side, or when I ask where I stand with a company.

How it works

  1. Record something
  2. Fix a mistake
  3. Look up
  4. Forbidden in this skill
Original SKILL.md headings · 65 lines, 559 words
SKILL.md preview
---
name: tracking
description: Record or look up my tracking (applications, follow-ups, interviews, answers, rejections, offers I found myself, notes). Use when the request starts with "Tracking", when I tell you what I did on my side, or when I ask where I stand with a company.
---

# My tracking

You keep my tracking in the `memory` MCP server. I talk to you simply, in French ("j'ai postulé chez Nova hier"): you put it in the right format.
**Nothing is ever deleted**: no row is erased or modified.
**Talk to me in French** (simple French), and write the `text` field in French.

## Record something

### 1. Understand
For each action in my message, find:

| Field | How |
|---|---|
| `type` | See the table below |
| `company` | The name I give |
| `date` | Format YYYY-MM-DD. Compute "hier" (yesterday), "lundi" (Monday)… from today's date given in the request. If I say nothing: leave it empty (= today) |
| `text` | A short sentence in French, with **my** information (channel, contact, next step…). Add nothing I did not say |

| What I say | `type` |
|---|---|
| postulé, candidaté, envoyé mon CV (applied, sent my CV) | `application` |
| relancé (followed up) | `follow_up` |
| entretien, call, visio, test (planned or done) | `interview` |
| positive or neutral answer, request for information | `answer` |
| refus, « pas retenu » (rejected) | `rejection` |
| je laisse tomber, plus intéressé(e) (I give up, no longer interested) | `dropped` |
| anything else | `note` |

### 2. Find the offer
Call `find` with the company name (or a word of the title).
- **A single offer** matches → use its `id` as `offer_id`.
- **Several** → show them to me (id, title, date) and ask which one.
- **None** → ask me: either you create the offer with `add_offer` (you need at least the title and the company; `source` = where I found it, e.g. `site_entreprise`), or you record the action without an offer (only the company).

### 3. Ask for my agreement
Before writing, show a summary (column names in French) and ask **« Je l'enregistre ? »**:

| Date | Type | Entreprise | Offre | Texte |
|---|---|---|---|---|
| 2026-10-26 | application | Nova | la_bonne_alternance:0123abc | Postulé via le site, contact : Mme Martin |

Several actions in one message → one single table, one single question.
**Call `add_tracking` or `add_offer` only after my "oui".** If I correct something, redo the table.
If you asked me a multiple-choice question (e.g. A or B) and my answer does not choose, **do not choose for me**: ask again, and write nothing.

### 4. Save
Call the tools, then confirm in one line with the number of each row (`num`).
If a tool returns an error, tell me what it says and suggest a fix.

## Fix a mistake
Nothing is erased. Add a row of type `note`: « Correction de la ligne n°X : … ». Ask for my agreement as usual.

## Look up
- "Où j'en suis ?", "mes dernières actions" → `history`.
- "Où j'en suis avec Nova ?" → `find`.

Answer briefly, with a table. Change nothing in the database while looking up.

## Forbidden in this skill
- Any action listed in "You must NEVER" in `CLAUDE.md` (no application, no message, no cover letter…).
- Writing to the database without my agreement (step 3).
- Inventing a date, a contact, a URL or any information.
- Calling `filter_already_seen` or `save_evaluations`: they are only for the offer search.

Versions

RepositoryScoreLicence
This page · dweuk/agent-stage-public90MIT
builderio/agent-native95MIT

Database snapshot: 13.11.2026 · package version 25e8f0bc8d96 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90newrole
    Job hunting with newrole.it, the person's job finder that runs on their own machine (MCP server "newrole"). Use when they ask to find, review or track job offers ("znajdź mi pracę", "oferty dla mnie", "co nowego", "szukam roli senior backend", "firmy jak Allegro", "oferty spoza…
  • 86job-tracker
    Go through the user's TakeMeUp job tracker — what's waiting for a reply, which follow-ups are due, what to update — and keep it current (add jobs, change status, set follow-up dates and notes). Use when the user asks about their applications, follow-ups, or job-search progress.
  • 86track-applications
    Check where the user's job applications stand with GetMattered, which employers confirmed them, and how many applications and credits the user has left. Use this skill whenever the user asks "did it go through", "what did I apply to", for an application status, a receipt or a…
  • 100weekly-plan
    Make a short "what to do this week" plan for the user's job search from the project board - follow-ups due, upcoming interviews and next steps, wishlist jobs to apply for, and issues with missing data. Use when the user asks what to do this week, what is due, or how to plan their job search.
  • 90follow-up
    Writes follow-up messages and full follow-up sequences for job seekers in any field - after no reply to a LinkedIn note, InMail or cold email; after applying; after a networking call; after interviews (thank-you notes); after silence from a recruiter; after rejection; and for…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.