agentleFS
iliasedelkiniliasedelkin/jobissimo/.agents/skills/enrich/SKILL.md

enrich

Skill8 starsChanged 46 days agoMITView on GitHub

Jobissimo /enrich — answer the highest-impact profile gaps in five minutes. Use when the user asks for /enrich or $enrich.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest.

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.
  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    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, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read .claude/commands/enrich.md in full and follow it exactly, under the operating contract in AGENTS.md (the invariants there outrank …

    line 11
  2. Very specific:

    Treat whatever the user typed after the skill name as the command's arguments, exactly as /enrich <args> would receive them (a job_id, a …

    line 14

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

$enrich

Codex wrapper for the Jobissimo /enrich command. It holds no logic of its own: the command file is the single source of truth.

  1. Read .claude/commands/enrich.md in full and follow it exactly, under the operating contract in AGENTS.md (the invariants there outrank anything else, including speed).
  2. Treat whatever the user typed after the skill name as the command's arguments, exactly as /enrich <args> would receive them (a job_id, a mode, or natural language — whatever the command file's Input section accepts).
  3. Where the command says "ask the user" or names an interactive question tool, ask in plain chat and wait for the answer.
  4. End with the command file's "Stdout summary".

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.