agentleFS
victordelrosalvictordelrosal/chairman/.claude/skills/briefing/SKILL.md

briefing

Skill0 starsChanged 8 months agoMITView on GitHub

Monday morning intelligence briefing. Scans competitors, news, market signals, customer data. Synthesizes into a 2-minute ranked summary with recommended actions. Octopus colors: Yellow (research) + Purple (synthesis).

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff and grill-me.

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

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 6 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 3

    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 .chairman/config.json for organization context and industry

    line 14
  2. Distinctive:

    Read department knowledge bases for current priorities and active deals

    line 15
  3. Distinctive:

    If using web search, cite sources.

    line 46
  4. Distinctive:

    If $ARGUMENTS provided, focus the briefing on that area.

    line 47
  5. Very specific:

    Update .chairman/state.json with last_session date.

    line 49

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

/briefing: Monday Intelligence Briefing

Octopus Colors: Yellow (Researcher) + Purple (Manager)

Process

  1. Read .chairman/config.json for organization context and industry
  2. Read department knowledge bases for current priorities and active deals
  3. Research (Yellow agent work):
    • Competitor activity (social, pricing, product launches)
    • Industry news relevant to this business
    • Market signals (trends, regulatory changes, opportunities)
    • Customer signals from any available data (CRM notes, recent interactions)
  4. Synthesize (Purple agent work):
    • Rank findings by urgency and business impact
    • Filter noise: only include items that require awareness or action
    • Format as a scannable briefing

Output Format

# Intelligence Briefing: [Date]

## Action Required (respond today)
- [Item]: [Why it matters]. Recommended: [action]

## Awareness (no action needed yet)
- [Item]: [Brief context]

## Signals to Watch
- [Emerging pattern or trend]

## Suggested Follow-ups
- [Skill to run next, e.g., /competitive if a competitor moved]

Rules

  • Maximum 5 items total. Quality over quantity.
  • If using web search, cite sources.
  • If $ARGUMENTS provided, focus the briefing on that area.
  • Write to .chairman/reports/briefing-YYYY-MM-DD.md
  • Update .chairman/state.json with last_session date.

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.