agentleFS
wangsy0247wangsy0247/multiagent-studio/skills/builtin/my-workflow/SKILL.md

my-workflow

Skill2 starsChanged 4 months agoMITView on GitHub

My custom daily workflow automation — organize tasks, generate standup notes, and format code. This is a personal skill I created for my own use.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    When I say "standup" or "daily update":

    line 15
  2. Distinctive:

    When I say "organize tasks" or "what should I work on":

    line 21
  3. Distinctive:

    Read any TODO.md or task files in the workspace

    line 22
  4. Distinctive:

    When I say "check format" or "lint check":

    line 27
  5. Distinctive:

    Run the appropriate linter for the project language

    line 28
  6. Distinctive:

    Use concise language, not verbose explanations

    line 33
  7. Distinctive:

    Always show the command that will be run before executing

    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

My Daily Workflow Skill

Purpose

Automate my common daily routines so I don't have to repeat the same instructions every day.

Workflows

Morning Standup

When I say "standup" or "daily update":

  1. List what I worked on yesterday (check git log for the past 24 hours)
  2. Summarize current branches and their status
  3. Generate a standup-format summary

Task Organization

When I say "organize tasks" or "what should I work on":

  1. Read any TODO.md or task files in the workspace
  2. Prioritize by urgency and dependencies
  3. Output a sorted task list with estimated effort

Code Format Check

When I say "check format" or "lint check":

  1. Run the appropriate linter for the project language
  2. Report issues grouped by severity
  3. Offer to auto-fix where possible

Preferences

  • Use concise language, not verbose explanations
  • Always show the command that will be run before executing
  • For git operations, never force-push to main/master

Templates

See templates/standup_template.md for the standup format.

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.