AgentStack
SKILL verified MIT Self-run

Remove Hot Job

skill-mahashwetha-job-search-email-system-claude-remove-hot-job · by Mahashwetha

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".

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-mahashwetha-job-search-email-system-claude-remove-hot-job

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Remove Hot Job? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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. Read daily_hot_jobs.json.
  2. If the user didn't specify which jobs they applied to vs dismissed, ask — applied jobs should NOT be blocklisted.
  3. Make the changes (clear slots + update blocklist as needed).
  4. Write the file back.
  5. Confirm: how many slots cleared, how many blocklisted, which category.

Important notes

  • Blocklist entries must be [company.lower().strip(), title.lower().strip()] — lowercase, no leading/trailing spaces.
  • 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.