AgentStack
SKILL verified MIT Self-run

Job Hunter

skill-oyi77-1ai-skills-job-hunter · by oyi77

Autonomous job hunting agent with state tracking, tailored applications, ATS optimization, and multi-platform

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

Install

$ agentstack add skill-oyi77-1ai-skills-job-hunter

✓ 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 Job Hunter? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Job Hunter

When to Use

Trigger phrases:

  • "job hunter"
  • "Help me with job hunter"

Use cases:

  • When the task matches this skill's domain expertise

When NOT to use:

  • For tasks outside this skill's scope

I am an advanced, state-aware job hunting agent. I don't just search; I remember what I've seen, track what I've applied to, and tailor my approach for every single job.

When NOT to Use

  • For one-off tasks that will never repeat
  • When the process requires human judgment at every step
  • When the cost of automation exceeds the cost of manual execution

Overview

Job Hunter automates workflow automation to reduce manual effort and increase reliability.

Workflow

# Example: Workflow automation
import schedule
import time

def run_workflow():
    data = fetch_data()
    processed = transform(data)
    deliver(processed)

schedule.every().hour.do(run_workflow)
while True:
    schedule.run_pending()
    time.sleep(60)
  1. Define triggers — Set up events or schedules that initiate the automation
  2. Configure inputs — Specify data sources and parameters
  3. Design pipeline — Define the sequence of automated steps
  4. Add error handling — Set up retries, alerts, and fallback paths
  5. Test end-to-end — Validate the full automation with realistic data
  6. Deploy and monitor — Activate and track performance

Configuration

  • Set trigger conditions (schedule, webhook, event)
  • Define input validation rules
  • Configure notification channels for alerts
  • Set retry policies and timeout limits

Best Practices

  • Start with simple automations and iterate
  • Add logging at every step for debugging
  • Use idempotent operations where possible
  • Test with edge cases before deploying

Anti-Rationalization

| Rationalization | Reality | |---|---| | "Manual is faster for one-off tasks" | One-off tasks become recurring. Automate early, save time later. | | "I will add error handling later" | You never do. Handle errors from day one. | | "Automation is overkill" | If you do it twice, automate it. If you do it daily, it is critical infrastructure. |

Process

  1. Reconnaissance — Gather target information, identify attack surface, enumerate services
  2. Analysis/Exploitation — Execute the technique, analyze results, document findings
  3. Reporting — Document IOCs, write findings, provide remediation recommendations

Verification

  • [ ] All steps executed successfully
  • [ ] Results validated against acceptance criteria
  • [ ] Error handling tested with edge cases
  • [ ] Documentation updated with findings

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.