Skip to content
Back to skills

Remove Hot Job

ASecurity

This skill should be used when the user wants to remove, clear, or blocklist jobs from the Hot Jobs section of the daily email. Triggers on phrases like "remove [company] from hot jobs", "clear hot jobs for [category]", "blocklist [company] hot job", "remove all senior java hot jobs", "clear [category] hot jobs", "I applied to [company] from hot jobs".

  • 9 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added May 28, 2026
toolspythongojavabackend

Security analysis

A100/100

Scanned September 26, 2026

npx -y skills add Mahashwetha/Job-search-email-system-claude --skill remove-hot-job --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Remove Hot Job?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Remove Hot Job
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mahashwetha-remove-hot-job/badge)](https://www.skillsdirectory.com/skills/mahashwetha-remove-hot-job)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: remove-hot-job
description: This skill should be used when the user wants to remove, clear, or blocklist jobs from the Hot Jobs section of the daily email. Triggers on phrases like "remove [company] from hot jobs", "clear hot jobs for [category]", "blocklist [company] hot job", "remove all senior java hot jobs", "clear [category] hot jobs", "I applied to [company] from hot jobs".
---

# Remove Hot Jobs

Manage the hot jobs list in `daily_hot_jobs.json`. Hot jobs are sticky LinkedIn listings shown at the top of the daily email, 5 per category (or 8 for Tech Lead / AI categories).

## Key concepts

- **current_jobs**: dict of category → list of job objects. Clear a slot by removing from this list — it backfills on next run.
- **blocklist**: list of `[company, title]` pairs. Blocklisted jobs never reappear in that category.
- If a job was **applied to** (company is in the tracker), do NOT blocklist it — the system auto-removes tracker companies naturally.
- If a job is being **dismissed without applying**, blocklist it so it doesn't come back.

## Categories (exact keys in JSON)
- `Senior Java`
- `Backend Java`
- `Product Owner`
- `Assistant Project Manager`
- `Tech Lead / Lead Developer`
- `AI / GenAI Engineer`

## What to do based on what the user says

**Remove a single job** (applied or dismissed) — remove it from `current_jobs[category]`. If dismissed (not applied), also add `[company.lower(), title.lower()]` to `blocklist`.

**Clear all jobs in a category** — set `current_jobs[category] = []`. For each job, blocklist it unless the user says they applied to it (or it's already in the tracker).

**Remove from blocklist** — find and delete the matching `[company, title]` pair from the `blocklist` array.

**List current hot jobs for a category** — read and print `current_jobs[category]`.

## Steps

1. If the user didn't specify which jobs they applied to vs dismissed, ask — applied jobs should NOT be blocklisted.
2. For each job to blocklist, run the script:
   ```
   python .claude/skills/remove-hot-job/scripts/blocklist_job.py "Company Name" "Job Title"
   ```
   Run from the project root (`C:/Users/mahas/Learnings/claude-job-agent`).
   - Title is optional — omit to blocklist all jobs from that company.
   - The script removes from `current_jobs` AND adds to blocklist in one shot.
   - Uses `ensure_ascii=False` so no encoding issues.
3. Confirm output to the user: removed from current_jobs + blocklisted.

**Block ALL current hot jobs** ("block all daily jobs"): one command instead of one run per job:
```
python .claude/skills/remove-hot-job/scripts/blocklist_job.py --all --dry-run   # preview
python .claude/skills/remove-hot-job/scripts/blocklist_job.py --all             # apply
```
It automatically skips companies already in the tracker (applied jobs clear naturally).

## Important notes
- Clearing slots triggers backfill on the next daily run (11:00 AM).
- Do NOT run the daily script after editing — changes take effect on the next scheduled run.
- Never manually edit `daily_hot_jobs.json` — always use the script to avoid encoding errors.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.