Individual skill
automate-me
Create a personal mode skill from recurring workflow patterns in available history. Use when the user wants their own agent style encoded.
skills/automate-me/SKILL.md
Source commit 79595c97d47b5400034fb985e67f1a00389a81af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 22
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- pstack Repository topic
- cline Repository topic
- copilot Repository topic
- gemini Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 832 bytes
Read excerpt
# Automate Me
1. Gather a representative sample of the user's actual completed workflows from available, authorized history. Do not infer private history you cannot access.
2. Extract repeated triggers, decisions, quality gates, preferred artifacts, and successful repair loops. Ignore one-off stylistic quirks unless explicitly requested.
3. Separate universal engineering principles from user-specific routing preferences.
4. Draft a `<name>-mode` Agent Skill that routes through existing skills rather than duplicating them.
5. Validate triggers against positive and negative examples, then present the generated skill and evidence behind each rule.