Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
OpenSpec
v1.0.0Spec-driven development with OpenSpec CLI. Use when building features, migrations, refactors, or any structured development work. Manages proposal → specs → design → tasks → implementation workflows. Supports custom schemas (TDD, rapid, etc.). Trigger on requests involving feature planning, spec writing, change management, or when /opsx commands are mentioned.
⭐ 0· 3.2k·11 current·11 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name, description, and instructions consistently describe a CLI-driven spec/workflow tool (OpenSpec). The commands and artifacts (proposal, specs, design, tasks) match the stated purpose. One note: the SKILL.md instructs installing @fission-ai/openspec from npm even though the skill bundle includes no install spec or provenance information; that is coherent with a CLI-based skill but means the runtime depends on a third-party npm package not included in the registry metadata.
Instruction Scope
Instructions are scoped to project-local flows (creating changes, writing artifacts into openspec/changes/<name>/, validating, archiving). They do not instruct reading unrelated system files or environment variables. They do instruct the agent/user to write files into the repository and to auto-generate a Claude integration under .claude/skills — review any generated files for unexpected content (API keys, endpoints) before committing.
Install Mechanism
There is no formal install spec in the skill bundle (lowest disk risk), but SKILL.md tells users to run `npm install -g @fission-ai/openspec@latest`. Global npm installs execute third-party code and produce binaries; verify the package publisher, inspect the package source, or prefer a non-global/local invocation (npx or container) if you want to avoid implicit code execution. The npm package name is not a known built-in; absence of homepage/source in the registry metadata reduces provenance.
Credentials
The skill declares no required environment variables, credentials, or config paths. SKILL.md does not attempt to read environment variables or request credentials. The main proportionality concern is operational: the CLI will modify project files and may add integration files (.claude/skills); those are appropriate for its purpose but should be inspected.
Persistence & Privilege
Skill does not request always:true and allows model invocation (default). It does, however, instruct installing a CLI that will create persistent project files (openspec/, .claude/skills/). This is expected for a development tool but warrants review of any generated files before committing, and cautious handling of the global npm install step.
Assessment
This skill appears to be what it says: a CLI-based spec/workflow helper that writes artifacts into your project. Before you install or run it: 1) Verify the npm package (@fission-ai/openspec) on the npm registry or GitHub — check publisher, source code, and recent versions. 2) Prefer non-global usage (npx or local install) or inspect the package contents before running a global install. 3) When you run the CLI, review any files it creates (openspec/, openspec/config.yaml, .claude/skills/*) for secrets, endpoints, or unexpected scripts before adding them to source control. 4) If you need higher assurance, run the install in an isolated environment (container/VM) and inspect the package source and behavior there. If you want, I can list the concrete checks to run on the npm package or draft a safe install procedure (npx, sandboxed run).Like a lobster shell, security has layers — review code before you run it.
latestvk9759aky3aqmwdbbegfzywhhan805xz3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.