Claude Skill

status

Say where the job search stands in a few lines. Use when the user says /status, "where am I", "what happened", "how many did I send", "what is waiting for me", or "what does this cost".

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download qbeka-jev-job-search-.claude_skills_status-0f99505.zip · 0 KB

Install

skills CLI npx skills add https://github.com/qbeka/jev-job-search/tree/main/.claude/skills/status
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install qbeka-jev-job-search@llmmart
Git git clone https://github.com/qbeka/jev-job-search.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole qbeka/jev-job-search collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

/status

Run these and give one short answer, not four dumps:

npx jev status
npx jev doctor
npx jev cost
npx jev schedule status

Say, in this order and only what applies:

  1. Sent: today and in total.
  2. Waiting for you: each form, what it asks for, and that /resume picks it up after they have done it in the tool's Chrome window.
  3. Left for you: how many are on the by-hand list, and the two or three most common reasons. npx jev log --manual lists them.
  4. Queue: how many jobs are ready to apply to, and how old the search is. Offer /discover when it is more than a day old.
  5. Accounts and the daily run: one line each, only if set up.
  6. Cost: what JEV has cost. Claude runs on their subscription.
  7. Next step: the one thing doctor names, as a slash command where there is one (/setup, /discover, /apply, /accounts, /daily, /resume, /report).

Never print a path, an id or a number they did not ask for when a sentence will do. /report is the full picture, in a page.

Files (jev-job-search)
  • SKILL.md 1.3 KB
    ---
    name: status
    description: Say where the job search stands in a few lines. Use when the user says /status, "where am I", "what happened", "how many did I send", "what is waiting for me", or "what does this cost".
    model: claude-sonnet-5-5
    effort: low
    ---
    
    # /status
    
    Run these and give one short answer, not four dumps:
    
    ```
    npx jev status
    npx jev doctor
    npx jev cost
    npx jev schedule status
    ```
    
    Say, in this order and only what applies:
    
    1. **Sent**: today and in total.
    2. **Waiting for you**: each form, what it asks for, and that `/resume`
       picks it up after they have done it in the tool's Chrome window.
    3. **Left for you**: how many are on the by-hand list, and the two or
       three most common reasons. `npx jev log --manual` lists them.
    4. **Queue**: how many jobs are ready to apply to, and how old the search
       is. Offer `/discover` when it is more than a day old.
    5. **Accounts and the daily run**: one line each, only if set up.
    6. **Cost**: what JEV has cost. Claude runs on their subscription.
    7. **Next step**: the one thing `doctor` names, as a slash command where
       there is one (`/setup`, `/discover`, `/apply`, `/accounts`, `/daily`,
       `/resume`, `/report`).
    
    Never print a path, an id or a number they did not ask for when a sentence
    will do. `/report` is the full picture, in a page.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.