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

report

Skill368 starsChanged 5 days agoMITView on GitHub

Open the user's dashboard, the main screen of the tool. Use when the user says /report, "show me my applications", "how is the search going", "what needs me", "open the dashboard", or wants to answer a form's question, change a status, or turn the daily run on or off without typing commands.

104 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use genie-hacks, opportunities and 10 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.
  • automagik-devSkill

    genie-hacks

    Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.

    Also in 3 projects that use this

  • ansvisorSkill

    opportunities

    Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.

    Also in 3 projects that use this

  • automagik-devSkill

    workfly

    Discover a procedure and build its saved workflow — dynamic discovery, drafted script, adversarial verification, landed in the catalog.

    Also in 3 projects that use this

  • soilmassSkill

    export

    Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.

    Also in 6 projects that use this

  • mmaripanguecSkill

    consistency

    Read-only cross-consistency analysis between a spec and the rest of the factory's artifacts (business rules, ADRs, as-is, .claude/rules rules, task plan). Use before the DoR gate and the Architecture gate, or when asked to "analyze consistency" of a spec.

    Also in 3 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 4 projects that use this

  • +4 more from automagik-dev

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 76 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from the repo root:

    line 10
  2. Distinctive:

    Applications: Every job, with tabs, a filter, a status select, a notes box, and the reply that came back.

    line 37

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

/report: the dashboard

Run from the repo root:

npx jev report --open

It starts a page on the user's own machine (http://127.0.0.1:4545) and opens it. Nothing leaves the machine. The command keeps running until they press Ctrl-C. The page has four screens:

  • Today. One line (sent today, waiting, ready to apply to), the totals, and three small charts.
  • Needs you. Everything only they can do, each with its button:
    • a question a form asked that their profile could not answer. They type or pick the answer and press "Save for next run". Nothing is sent then: the job goes back in the queue and the next /apply or daily run fills it with that answer. "Remember for future applications" keeps the answer as a standing answer. A question about the right to work has no box: that answer is one per country and lives in the profile (/profile).
    • a form open and waiting (an emailed code, a robot check, a sign-in): "Show the form" brings it to the front, "Find the email" opens their mail at a search for it. They do it, then /resume.
    • a form clicked and never confirmed: "I got a confirmation", or "It was not sent".
    • an email the tool could not place: they pick the application and what it says.
  • Applications. Every job, with tabs, a filter, a status select, a notes box, and the reply that came back.
  • Automation. The daily run: an "Apply automatically" switch with a time, the next run, "Pause future runs" (removes the schedule), "Stop it after this application" while a run is working, their daily rules as a form, and today's result in one line. Turning the switch on installs the schedule; that is their click, not yours.

npx jev report --static applications/report.html writes a snapshot page with Today and Applications only, for keeping or sending. Nothing can be changed from a snapshot.

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.