dev-test
v1.0.0Structured development and testing SOP for implementing code changes. Covers codebase study, minimal focused implementation, test writing patterns, test exec...
⭐ 0· 68·0 current·0 all-time
byBijin@sliverp
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 (development & testing SOP) matches the SKILL.md content: repository study, focused implementation, tests, running test suites, and diff review. Nothing in the metadata or instructions requires cloud credentials, unrelated binaries, or other capabilities beyond typical repository access.
Instruction Scope
Runtime instructions are prescriptive and narrowly scoped to reading repo files (CONTRIBUTING.md, config files, modules, tests), writing focused code changes, running tests (pytest/npm/go test), and reviewing diffs. The guidance does not direct the agent to read unrelated system files, exfiltrate data, or call external endpoints beyond common test tooling.
Install Mechanism
No install spec or code files are present; this is instruction-only. Nothing will be downloaded or written to disk by the skill itself, so there is minimal installation risk.
Credentials
The skill does not declare or require any environment variables, credentials, or config paths. The operations it describes (reading repo files, running tests) reasonably require only repository access and standard developer tooling.
Persistence & Privilege
always is false and there is no request to modify other skills or persist configuration. The skill does not ask for permanent presence or elevated privileges beyond normal agent execution rights.
Assessment
This skill is an instructional SOP and is coherent with its stated purpose. It does not request credentials or install code, so direct technical risk from the skill content is low. Before enabling: ensure the agent/runtime that will execute these instructions has appropriate permissions (so it cannot access secrets or private systems you don't want exposed), and confirm your repository does not contain hardcoded secrets (the SOP instructs you to check diffs for secrets, which is good practice). Because the skill source is 'unknown' and unverified, treat it as advisory: review the SKILL.md yourself to ensure the workflow aligns with your team's processes and restrict autonomous agent execution if you want to avoid any automated edits or test runs without human oversight.Like a lobster shell, security has layers — review code before you run it.
latestvk975xbh8s47zd2krdpvhstrc0983hb8h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.