Nola Squad
v1.0.0Nola — your AI engineering squad lead. Dispatches 14 specialist agents to build, test, review, and ship code. Use when the user needs software built, bugs fi...
⭐ 0· 49·0 current·0 all-time
by@flikq
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (multi-agent engineering lead) aligns with what the skill asks for and includes: an instruction-only SKILL.md and 14 agent role documents. The only required binary is git, which is expected given the Releaser agent's git/push responsibilities. No unexpected credentials, config paths, or unrelated binaries are requested.
Instruction Scope
Runtime instructions direct the lead agent to read the codebase, plan work, and spawn specialist agents which read files, run tests, start dev servers, fetch external data (Scraper), and push commits/PRs (Releaser). These actions are coherent with building/testing/shipping code, but they entail normal local/remote side effects (running commands, network access, and pushing to git remotes). The skill does not instruct the agent to exfiltrate secrets or to contact unknown endpoints outside normal development workflows.
Install Mechanism
No install spec or code files that would be written/executed at install time. The skill is instruction-only (SKILL.md + role docs), which minimizes install-time risk.
Credentials
The skill declares no required environment variables or credentials. That is proportional to an instruction-only orchestration skill. Note: pushing commits or starting dev servers uses the agent environment's existing git config, credentials, and network access — those are not requested by the skill but will be used if the agents run git push or start services.
Persistence & Privilege
always:false and default autonomous invocation settings are used. The skill does not request permanent system presence or modify other skills' configs in its instructions. Autonomous spawning of sub-agents is the intended function and is consistent with platform behavior.
Assessment
This skill looks coherent for orchestrating multi-agent software work, but be aware of the real-world side effects when you run it: agents may read your repository, run build/test commands, start local dev servers, fetch external URLs, and Releaser will push branches and create PRs using whatever git credentials are available in the running environment. Before enabling or invoking it: 1) Inspect the included agent preambles (agents/*.md) so you understand their behaviors and constraints; 2) Run it first against a safe/test repository or branch to observe actions; 3) Ensure no sensitive files (like .env) are present in the target workspace and that your git credentials are what you expect; 4) If you require tighter control, restrict the agent's ability to push or spawn sub-agents or remove/modify the Releaser and Scraper behaviors. If you want further checking, provide the exact repo or intended workflow and I can point out any agent lines that would act on specific files or commands.Like a lobster shell, security has layers — review code before you run it.
latestvk979rcr5zmqnp8gwzzh0nptkj983se6j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsgit
