agentleFS
Sign inStart free
edjchapmanedjchapman/claude-code-config/skills/status/SKILL.md

status

Skill8 starsChanged 19 days agoMITView on GitHub

Capture a quick status update and append it to today's daily log.

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 10 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 4 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 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

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 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 146 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. Distinctive:

    If no message is provided, ask the user:

    line 21
  2. Very specific:

    Create the ./standups/ directory if it doesn't exist

    line 32
  3. Distinctive:

    Use the current local time (24-hour format) for the timestamp.

    line 50
  4. Very specific:

    Important: If the file already exists but has no ## Status Updates section, add it before the first ## Session Summaries section (or at the …

    line 52
  5. Distinctive:

    Do NOT gather any additional data, run git commands, or produce lengthy output.

    line 63

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

Capture a quick status update and append it to today's daily log.

Arguments

$ARGUMENTS

  • Message: Free-text status update (required)
    • Examples: /status Finished auth flow for BIL-123, /status In code review for PR #456

Step 1: Parse Arguments

The full $ARGUMENTS text is the status message.

If no message is provided, ask the user:

"What's your status update?"

Step 2: Determine File Path

date +%Y-%m-%d
  • Log file path: ./standups/YYYY-MM-DD-log.md
  • Create the ./standups/ directory if it doesn't exist

Step 3: Create or Append to Daily Log

If the log file does not exist, create it with this header:

# Daily Log - DD Mon YYYY

followed by a blank line and the ## Status Updates section.

Append the timestamped entry under the ## Status Updates section:

- **HH:MM** - [message]

Use the current local time (24-hour format) for the timestamp.

Important: If the file already exists but has no ## Status Updates section, add it before the first ## Session Summaries section (or at the end of the file if no sections exist). Always append new entries at the end of the Status Updates section, before any other section.

Step 4: Confirm

Output a brief confirmation (2-3 lines max):

Status logged to ./standups/YYYY-MM-DD-log.md
> HH:MM - [message]

Do NOT gather any additional data, run git commands, or produce lengthy output. This command is for quick capture only.

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.

Check your setup, free