agentleFS
TheVellerTheVeller/claude-skills/skills/agent-operations/hallazgo/SKILL.md

hallazgo

Skill4 starsChanged 13 days agoMITView on GitHub

Use this when posting any report a human might read later — worker brief, GM daily, or Grok Bot rollup. Family not template: @author bot, emoji to skim, bullets, subheads, dense. Grok workflow: formato-hallazgo. Surfaces: Grok, Hermes, Claude.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Authorship: every finding tags the original bot with @Nombre so it can be traced up the stack.

    line 14
  2. Very specific:

    Verify before it moves up.

    line 16
  3. Distinctive:

    No peer-spam. No scout → Ignacio.

    line 40
  4. Very specific:

    Do not create Notion DBs or new ledger pages.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Reportes (formato hallazgo)

Hierarchy: staff → GM / room → Grok Bot → Ignacio 1:1. Scouts never write Ignacio. KEEP hunters (Vivienda, Inmobiliario, Vuelos → Levy; Gangas → Forja). Perks and other Forja staff → Forja.

Authorship: every finding tags the original bot with @Nombre so it can be traced up the stack. GMs and Grok Bot keep that tag when they roll up; they do not strip the scout.

Verify before it moves up. No invented numbers. n/d if missing. One real link per item. No code fences in anything Ignacio might read. Silence if nothing.

Format is a family close to 🎯 oferta · 🔗 link · ⭐ score · ➡️ next — improved and adapted per beat (listings, jobs, caja, learning). Keep the standard: emoji to cut visual load, bullets, short subheads, dense and skimmable.

Worker (short)

@Nombre del bot 🎯 oferta 🔗 un link ⭐ score ➡️ next (no A3)

Bullets and a short subhead are fine. Silence if nothing.

GM (daily, larger)

Same family. Keep @ of each scout on each TOP. Typical: período, TOPs, descartados N, pedido, A3 sí/no. To sala GMs, not Ignacio. Full GM format: reporte-gm.

Grok Bot (largest, frequent)

Pack verified briefs into Ignacio 1:1. Keep @hunter on each item. Report often. Quality bar = Gangas remates pack.

Rules

  • No peer-spam. No scout → Ignacio.
  • Do not create Notion DBs or new ledger pages. Mid-session: vault or GM chat. Session close: existing Notion ledger only; else stay vault and say ledger missing.

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.