Cycle

v1.1.0

Design custom workflow cycles for any domain. Create structured, repeatable processes that become persistent skills.

2· 941·0 current·0 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (designing reusable workflows) matches the content of SKILL.md, discovery.md, examples.md, and implementation.md. Nothing in the files asks for unrelated capabilities (cloud creds, system binaries, etc.).
Instruction Scope
Runtime instructions are limited to asking questions, defining phases, and describing how cycles map to files; they do not instruct the agent to read arbitrary system files, call external endpoints, or exfiltrate data. The guidance to 'delegate to sub-agent' is scope-limited and consistent with multi-step workflow orchestration.
Install Mechanism
No install spec and no code files; this is instruction-only so nothing is downloaded or written by an installer. Lowest-risk install profile.
Credentials
The skill declares no environment variables, credentials, or config paths and the instructions do not reference secrets or unrelated environment data.
Persistence & Privilege
implementation.md describes a 'state.md' for persisting preferences/patterns. The skill package itself does not request storage paths, but be aware that an agent using this guidance could create persistent files or stored state when implemented; that persistence is expected for this type of skill but you should confirm where such state is stored and who can access it.
Assessment
This skill is instruction-only and appears to do what it says: help design repeatable workflows and (optionally) persist them as simple skill files. Before installing or enabling it in an agent, confirm where any 'state' or generated skill files will be stored and who can read them (to avoid accidental exposure of sensitive notes). Also verify any future implementation that adds automation or file writes does not request unrelated credentials or external network endpoints.

Like a lobster shell, security has layers — review code before you run it.

latestvk971yxceq54t2nctnw7j3skm4d80ynrp

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments