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.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- code-reviewerSkill
- deep-researchSkill
- deployment-checklistSkill
- find-skillSkill
- system-architecture-reviewSkill
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
- Distinctive: line 15
When I say "standup" or "daily update":
- Distinctive: line 21
When I say "organize tasks" or "what should I work on":
- Distinctive: line 22
Read any TODO.md or task files in the workspace
- Distinctive: line 27
When I say "check format" or "lint check":
- Distinctive: line 28
Run the appropriate linter for the project language
- Distinctive: line 33
Use concise language, not verbose explanations
- Distinctive: line 34
Always show the command that will be run before executing
≈ “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.
Files
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":
- List what I worked on yesterday (check git log for the past 24 hours)
- Summarize current branches and their status
- Generate a standup-format summary
Task Organization
When I say "organize tasks" or "what should I work on":
- Read any TODO.md or task files in the workspace
- Prioritize by urgency and dependencies
- Output a sorted task list with estimated effort
Code Format Check
When I say "check format" or "lint check":
- Run the appropriate linter for the project language
- Report issues grouped by severity
- 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.
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
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.

