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
- dbareagimeno/enutheir own version, first seen Jul 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dbareagimeno/enu★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository131 other files it gives its agents.
- agent-contractSkill
- brand-chrome-loginSkill
- contexto-aristasSkill
- crear-bot-nicoSkill
- daily-standupSkill
- design-a-grok-botSkill
- drift-hunt-rosterSkill
- explain-grokbotSkill
- exportar-botSkill
- govern-agentic-osSkill
- grok-bot-project-opsSkill
- handoff-local-hermesSkill
- identity-pipelineSkill
- loop-corpSkill
- no-devSkill
- orca-handoffSkill
- panorama-de-flujoSkill
- reporte-gmSkill
- routine-healthcheckSkill
- sprint-parallelSkill
- transcript-healthcheckSkill
- getting-started-brandySkill
- getting-started-calendario-contenidoSkill
- getting-started-cazador-de-canalesSkill
- getting-started-cazador-de-vuelosSkill
- getting-started-cazador-gangasSkill
- getting-started-cazador-inmobiliarioSkill
- getting-started-cazador-programasSkill
- getting-started-cazador-sponsorsSkill
- getting-started-cazador-viviendaSkill
- getting-started-content-drafterSkill
- getting-started-data-scienceSkill
- getting-started-demand-hunterSkill
- getting-started-digital-storesSkill
- getting-started-directory-builderSkill
- getting-started-enrichment-deskSkill
- getting-started-event-hunterSkill
- getting-started-expense-managerSkill
- getting-started-gm-operacionesSkill
- getting-started-inbox-managerSkill
- getting-started-intake-intelSkill
- getting-started-intelligence-gmSkill
- getting-started-join-a-startupSkill
- getting-started-last30daysSkill
- getting-started-life-opsSkill
- getting-started-luma-taggingSkill
- getting-started-market-watcherSkill
- getting-started-meta-vaultSkill
- getting-started-musa-designerSkill
- getting-started-plantillas-notionSkill
- getting-started-product-hunterSkill
- getting-started-publisherSkill
- getting-started-pulso-brandSkill
- getting-started-pulso-diaSkill
- getting-started-renewals-hunterSkill
- getting-started-saves-archivistSkill
- getting-started-scraping-deskSkill
- getting-started-seo-deskSkill
- getting-started-sliderSkill
- getting-started-swe-outer-loopSkill
- The first 60 shown.
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
- Very specific: line 14
Authorship: every finding tags the original bot with @Nombre so it can be traced up the stack.
- Very specific: line 16
Verify before it moves up.
- Distinctive: line 40
No peer-spam. No scout → Ignacio.
- Very specific: line 41
Do not create Notion DBs or new ledger pages.
≈ “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.
Files
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.
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
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.

