SpecClaw

Spec-driven development framework for OpenClaw. Propose features, generate specs, spawn coding agents, validate implementations.

This skill is powerful and generally coherent with its purpose, but proceed with caution: - Review config.yaml before using: the skill will run test/lint/build commands and may auto-commit/merge; ensure commands are safe and auto-merge behavior is acceptable. - External integrations (GitHub issue sync, Discord notifications) are mentioned but no credentials are declared. Inspect gh-sync.sh and notification-related scripts to see which environment variables or auth methods they use; supply credentials only if you trust the code and repository. - The skill spawns coding agents that receive file contents (up to 500 lines per file). If your repo contains sensitive secrets, consider cleaning or isolating the repository (or disabling automation) before running builds. - There's a small path inconsistency in the docs: SKILL.md sometimes references bash skill/scripts/*. The actual scripts are in scripts/. Confirm paths used at runtime (OpenClaw may mount skill files under a different root) so commands invoked by the agent will work as intended. - Test in a disposable or sandbox repository first. Disable automation/cron until you’ve validated behavior. If you need the GitHub/Discord features, audit the specific scripts (gh-sync.sh, notification code) to confirm what tokens they read and how they transmit data. If you'd like, I can: (1) list the exact places where external tokens would be needed (search gh-sync.sh, notification code), (2) scan the bundled scripts for code that posts to external endpoints or reads environment variables like GITHUB_TOKEN, DISCORD_WEBHOOK, etc., or (3) summarize what config.yaml options control auto-merge and automation.

Type: OpenClaw Skill Name: specclaw Version: 0.6.1 The specclaw skill bundle implements a complex spec-driven development framework that orchestrates sub-agents to automate code changes. It is classified as suspicious due to the use of 'eval' in 'scripts/build.sh' and 'scripts/verify.sh' to execute shell commands (test, lint, and build) defined in the 'config.yaml' file. This creates a significant Remote Code Execution (RCE) vulnerability if the configuration is manipulated. Additionally, 'scripts/gh-sync.sh' handles GitHub authentication tokens to interact with the GitHub API (api.github.com). While these capabilities are aligned with the stated purpose of a build and synchronization engine, the lack of input sanitization for executed commands represents a high-risk behavior without evidence of intentional malice.