How do I install the Test Run skill?

Run npx skillmds@latest add mahashwetha/test-run in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Test Run safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Test Run?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Test Run free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Test Run?

Mahashwetha (@mahashwetha) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Test Run by mahashwetha — Agent Skill

Name: Test Run
Author: Mahashwetha

Test Run

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

Mahashwetha 880d81c 1.5 KB Updated Sep 17, 2026

File contents

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: C:/Users/mahas/Learnings/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.

Frequently asked questions