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

status

Skill0 starsChanged 8 months agoMITView on GitHub

Show current organizational state - active departments, pending assignments, escalations, recent activity. The Chairman's dashboard.

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 9 more.

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

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 6 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 7 projects that use this

  • MistralSkill

    import

    Import the user's setup from other coding CLIs (Claude Code, Codex, OpenCode) into Vibe — instructions, skills, subagents, commands, hooks, MCP servers, permissions, and plugins. Load when the user wants to switch to Vibe, import or reuse another CLI's configuration, or asks whether a file from another CLI works in Vibe.

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • VercelSkill

    next

    Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.

    Also in 11 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 157 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read and display the current state of the Chairman organization.

    line 10
  2. Very specific:

    Read .chairman/config.json for organization info

    line 14
  3. Very specific:

    Read .chairman/state.json for current state

    line 15
  4. Very specific:

    If the organization is not yet configured, tell the user to run /onboard.

    line 44

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

/status: Organizational Dashboard

Read and display the current state of the Chairman organization.

Process

  1. Read .chairman/config.json for organization info
  2. Read .chairman/state.json for current state
  3. List active departments from departments/
  4. Count pending items in .chairman/assignments/, .chairman/escalations/, .chairman/reports/
  5. Show recent activity (last 5 reports or assignments by date)

Output Format

# Chairman Status: [Organization Name]
Last session: [date]
Trust level: [new/established/mature]

## Departments
- [dept]: [status] | Knowledge base: [file count] files
- ...

## Pending
- Assignments: [count]
- Escalations: [count] (REVIEW THESE)
- Reports: [count] unread

## Recent Activity
- [date] [department] [action summary]
- ...

## Suggested Next Action
[Based on day of week and pending items, suggest the appropriate skill]

If the organization is not yet configured, tell the user to run /onboard.

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.