agentleFS
giorgosngiorgosn/diavgeia-watchdog/skills/write-brief/SKILL.md

write-brief

Skill2 starsChanged 5 months agoMITView on GitHub

Use when the user wants to turn a verified procurement lead into a written briefing, story memo, or report — "write this up", "draft a brief", "summarize the finding for publication".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. sparkline-ventures/product-eval★ 15same 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Do not write a brief on an unverified lead.

    line 12
  2. Distinctive:

    If not, stop and route them back to investigate / the methodology.

    line 18
  3. Distinctive:

    Leads, not accusations: Use "the records show", "appears", "warrants scrutiny" — not "proves" or "is guilty".

    line 32
  4. Distinctive:

    Every factual claim carries its evidence link.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Write a verified-lead briefing

Turn a lead the user has already verified into a careful, citation-backed write-up.

Before writing — confirm verification

Do not write a brief on an unverified lead. Confirm with the user that they have:

  • opened the source documents (the evidence links) and the figures/dates check out;
  • considered the legitimate explanations (framework contract, emergency, distinct lots, per-patient medical supply — see docs/METHODOLOGY.md);
  • a plan to seek right-of-reply from the authority and supplier.

If not, stop and route them back to investigate / the methodology.

Brief structure

  1. Headline — neutral and factual ("X awarded Y N contracts totalling €Z, each under the €30k tender threshold"), never a verdict ("X is corrupt").
  2. The pattern — what the data shows: counts, amounts, dates, the threshold, the signer.
  3. The connections — supplier's other authorities, the official's network, owners (ΓΕΜΗ).
  4. Evidence — a numbered list of the source decision/contract links (ADA/ADAM).
  5. Caveats & open questions — what could legitimately explain it; what still needs checking.
  6. Right-of-reply — note that comment was/should be sought.

Tone

  • Leads, not accusations. Use "the records show", "appears", "warrants scrutiny" — not "proves" or "is guilty".
  • Every factual claim carries its evidence link.
  • Plain language; define Greek terms (κατάτμηση = contract-splitting; the ~€30k threshold).

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.