agentleFS
qbekaqbeka/jev-job-search/.claude/skills/inbox/SKILL.md

inbox

Skill368 starsChanged 5 days agoMITView on GitHub

Check the user's connected Gmail for replies to applications they sent (received, rejected, an assessment, an interview, an offer) and put them on the record. Use when the user says /inbox, "did anyone reply", "check my email for responses", or "any interviews".

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use journey, weekly and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MeshJSSkill

    journey

    Create session learning logs that persist institutional memory across Claude Code sessions.

    Also in 3 projects that use this

  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 3 projects that use this

  • endlessblinkSkill

    task

    Create a new task in MASTER_PLAN.md with auto-generated sequential IDs. Supports TASK, BUG, FEATURE, and INQUIRY types. Triggers on "/task", "add task", "new task", "create task", "track this".

    Also in 3 projects that use this

  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 4 projects that use this

  • genomewalkerSkill

    tasks

    Browse and resume tasks, threads, and background jobs across sessions

    Also in 3 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Run npx jev inbox, or npx jev inbox --days <n> when they gave a number.

    line 11
  2. Distinctive:

    Never read the user's mail any other way, never open or quote an email's body, and never reply to anyone.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 23 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

/inbox

Run npx jev inbox, or npx jev inbox --days <n> when they gave a number. It needs Gmail connected, read-only (/accounts gmail). If it says Gmail is not connected, say that this is optional and what it does, and stop.

It reads only each email's sender, subject and the short preview Gmail itself shows, never the body. What it is sure of goes on the application's record: the "Reply" column in /report and in applications/all.csv. A confirmation also settles an application that was clicked and never confirmed.

Tell the user, in this order:

  1. Interviews, assessments and offers, by company. These need them.
  2. How many said no, and how many only confirmed receipt.
  3. How many emails it was not sure about. Those wait under "Needs you" in the dashboard: /report.

Never read the user's mail any other way, never open or quote an email's body, and never reply to anyone.

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.