agentleFS
MahashwethaMahashwetha/Job-search-email-system-claude/.claude/skills/test-run/SKILL.md

test-run

Skill12 starsChanged 11 days agoMITView on GitHub

This skill should be used when the user wants to manually trigger, test, or run the job search scripts — either the daily job search email or the remote job search email. Triggers on phrases like "run daily jobs", "test the remote search", "trigger the job email", "run it manually", "send the job digest now", "test remote job search".

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run daily_job_search.py. This reads List.xlsx, fetches hot jobs from LinkedIn, and sends the styled HTML digest email.

    line 12
  2. Very specific:

    Only omit --no-save when running for real (i.e.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Test Run — Manual Script Execution

Manually trigger the daily or remote job search scripts outside their scheduled runs. Run all commands from the project root: claude-job-agent/.

Daily job search

Run daily_job_search.py. This reads List.xlsx, fetches hot jobs from LinkedIn, and sends the styled HTML digest email.

To force a full hot jobs refresh (re-fetch everything), delete daily_hot_jobs.json before running.

Remote job search

Run remote_search/remote_job_search.py.

Always add --no-save for test runs. Without it, previous_jobs.json gets overwritten and the NEW flag detection breaks for the real scheduled run. The Excel file still gets updated either way.

Only omit --no-save when running for real (i.e. as a substitute for the scheduled run).

Common issues

  • config.py not found — copy config.template.py to config.py and fill in credentials.
  • PermissionError on Excel — the script handles this with a temp copy fallback, but closing List.xlsx first is cleaner.
  • Email not received — check spam, verify EMAIL_CONFIG in config.py.

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.