Testing Workflow

Meta-skill that orchestrates comprehensive testing across a project by coordinating testing-patterns, e2e-testing, and testing agents. Use when setting up testing for a new project, improving coverage for an existing project, establishing a testing strategy, or verifying quality before a release.

This appears to be a documentation-only meta-skill for organizing testing work — it does not request secrets or install code on its own. Before installing or running commands mentioned in the README: (1) inspect any remote repository URL (the 'npx add' GitHub tree link) before executing it; (2) when the orchestration routes to other skills (testing-patterns, e2e-testing, etc.), review those skills' SKILL.md files to ensure they are coherent and don't request credentials or perform installs you don’t expect; (3) be cautious copying files from paths like ~/.ai-skills or running commands that originated from unknown sources; and (4) as a final check, ensure CI integrations and test-run steps in your repository do not inadvertently expose secrets (for example, by printing env vars to logs). If you want higher confidence, provide the SKILL.md files for the routed skills so they can be evaluated as well.

Type: OpenClaw Skill Name: testing-workflow Version: 0.1.0 The skill instructs the AI agent to perform file write operations, specifically to "commit [the Testing Strategy Template] to the repository" as detailed in SKILL.md. While this action is aligned with the stated purpose of documenting a testing strategy, it represents a file system access capability that, without further safeguards, could be exploited through prompt injection to write arbitrary or malicious content to the repository. Additionally, the README.md includes an `npx add` command for installation, which, while user-facing, introduces a supply chain risk if the remote source (`https://github.com/wpank/ai/tree/main/skills/testing/testing-workflow`) were compromised.