agentleFS
MahashwethaMahashwetha/Job-search-email-system-claude/.claude/skills/reject-job/SKILL.md

reject-job

Skill12 starsChanged 12 days agoMITView on GitHub

This skill should be used when the user wants to reject, hide, or filter out a remote job from future email digests. Triggers on phrases like "reject this job", "hide [company]", "add to reject list", "don't show [company] again", "remove [company] from results", or when reviewing remote job emails and marking jobs as not relevant.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the appropriate script command.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reject Remote Job

Manage the remote jobs blocklist. Jobs on this list are filtered out of all future remote job emails.

The blocklist lives in remote_search/rejected_remote.json and is managed via remote_search/reject_remote.py (run from the project root).

What to do based on what the user says

Reject a specific job — run the script with company name and job title as arguments.

Reject all roles from a company — run the script with the company name and an empty string as the title.

Reject everything from the last email — run the script with --all. This bulk-rejects all jobs from previous_jobs.json (the last run).

Restore a rejected job — run the script with --remove followed by the company and title.

Show all rejections — run the script with --list.

Matching rules — important

  • Matching is case-insensitive substring. "grafana" matches "Grafana Labs".
  • Special characters (é, ®, ™) must match exactly — double-check character by character if a company name has accents or symbols.
  • An empty title rejects all roles from that company permanently.
  • To undo, use --remove with the exact same strings used when adding.

Steps

  1. Identify what the user wants to reject (company, title, or both).
  2. Double-check the company name spelling, especially for special characters.
  3. Run the appropriate script command.
  4. Confirm the output shows the entry was added and the new total count.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.