QA & Test Engineering Command Center
v1.0.0Comprehensive QA system for planning strategy, writing tests, analyzing coverage, automating pipelines, performance and security testing, defect triage, and...
⭐ 1· 897·5 current·5 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (comprehensive QA/test engineering) match the SKILL.md content: strategy, unit/integration/E2E patterns, performance and security testing, CI/CD gating, and defect triage. The README and instructions are consistent with a QA advisory/automation role.
Instruction Scope
SKILL.md gives runtime guidance that includes starting test servers, running test databases/migrations, recording/replaying external API responses, and configuring CI gates. These actions are reasonable for a QA skill, but they imply the agent may need access to the codebase, test infrastructure, or test credentials to be useful — the instructions themselves do not ask for those credentials, but they assume the agent will be granted them by the environment.
Install Mechanism
No install spec and no code files are included; this is instruction-only so nothing is downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables, binaries, or config paths. The SKILL.md mentions mocking environment variables and interacting with services for testing, which is appropriate contextually and does not demand extraneous credentials from the user.
Persistence & Privilege
always is false and the skill does not request persistent system-level presence or attempt to modify other skills. Autonomous invocation is allowed (platform default) but not unusual for this type of skill.
Assessment
This skill is internally consistent and doesn't ask for secrets or installs. Before enabling it, consider: 1) only grant the agent the minimum access needed (avoid giving production DB or CI tokens; use test/staging credentials), 2) run it in a sandboxed environment or with limited network access if it will execute tests or start services, 3) review any agent actions that would modify infrastructure (migrations, seeding) and require explicit approval, and 4) be cautious with external links or paid context packs in the README — they are marketing and not required for the skill to function. If you want higher assurance, ask the publisher for provenance (who maintains it) or request a version that includes automated checks and explicit runtime permissions. Like a lobster shell, security has layers — review code before you run it.
automationvk97erhpwy5ax6z5e9cqb9qggmx816qhmci-cdvk97erhpwy5ax6z5e9cqb9qggmx816qhmdevopsvk97erhpwy5ax6z5e9cqb9qggmx816qhme2evk97erhpwy5ax6z5e9cqb9qggmx816qhmintegrationvk97erhpwy5ax6z5e9cqb9qggmx816qhmlatestvk97erhpwy5ax6z5e9cqb9qggmx816qhmperformancevk97erhpwy5ax6z5e9cqb9qggmx816qhmqavk97erhpwy5ax6z5e9cqb9qggmx816qhmsecurityvk97erhpwy5ax6z5e9cqb9qggmx816qhmtestingvk97erhpwy5ax6z5e9cqb9qggmx816qhmunit-testvk97erhpwy5ax6z5e9cqb9qggmx816qhm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.