Agently Playbook
v0.1.0Use when the user wants to build, initialize, validate, optimize, or refactor a model-powered assistant, internal tool, automation, evaluator, or workflow fr...
⭐ 0· 90·0 current·0 all-time
by@maplemx
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the SKILL.md and reference files: this is a high-level playbook for shaping model-powered assistants and routing to leaf Agently capabilities. It does not request unrelated credentials, binaries, or system access.
Instruction Scope
The instructions are developer-facing guidance (project splitting, async-first rules, settings patterns) and do not direct the agent to read arbitrary user files or exfiltrate data. They do recommend using ${ENV.xxx} placeholders and validating env values at initialization — appropriate for a project playbook, but something to be aware of because downstream implementation steps may prompt for or require environment secrets.
Install Mechanism
No install spec or code files — instruction-only skill. Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables or credentials. The references and SKILL.md recommend best-practice use of ${ENV.xxx} and .env patterns for implementations, which is proportionate to the stated purpose but means real implementations will later request provider keys (expected for downstream, implementation-specific skills).
Persistence & Privilege
always is false and there are no install hooks or config paths. The skill does not request permanent presence or system-level privileges.
Assessment
This skill is a high-level design/playbook and appears coherent and low-risk by itself. Before using it in a production agent, remember: (1) it encourages using environment variables and .env patterns — do not paste secrets into chat or prompts; store provider keys in secure vaults or protected env variables; (2) follow-up work will be routed to specific agently-* leaf skills that may need provider credentials — review those leaf skills separately before granting secrets; (3) because it's instruction-only, it won't install code, but any code you scaffold based on its advice will. If you need the agent to work with live credentials, only provide them to trusted code/skills and verify those skills' install and env requirements first.Like a lobster shell, security has layers — review code before you run it.
latestvk9712n232s2rvm75v3vkvdn965836k65
License
MIT-0
Free to use, modify, and redistribute. No attribution required.