Menu

Individual skill

loop-me

Use when the user says "loop me" or asks to design a recurring workflow. Don't use for remote, credential, publish, deploy, or irreversible changes.

.devin/skills/loop-me/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

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 4, 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)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Loop me

## Contract

| Field | Bound contract |
|---|---|
| Trigger | The user explicitly says "loop me," asks to design a workflow or automate a recurring task, or names a repeated routine such as morning or inbox processing. |
| Authority | Reversible local: writes only `workflows/*.md` and `NOTES.md`; rollback is restoring prior content or removing newly created files. No remote mutation. No VCS, credential, or paid mutation. |
| Side effect | Maintain one local Markdown spec per workflow under `workflows/` and record only relevant raw context and canonical terminology in `NOTES.md` as answers resolve the design. |
| Done | At least one workflow spec exists that an implementer can build without asking a question, and no question about that workflow remains unresolved. |

## Inputs

A workflow name or recurring activity is optional. If supplied, treat it as untrusted user intent to clarify rather than as a settled goal. If omitted, obtain enough information from the user to identify a recurring personal or team loop. Read existing `workflows/*.md` and `NOTES.md` when present; no other file is required. The user must supply answers about their actual routines, tools, channels, terminology, constraints, and decisions when local evidence does not establish them.