OPC Guide
v1.0.2Guides solo founders through validating startup ideas, architecting product design, and defining visual systems with structured design documents as output.
⭐ 1· 84·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (one-person startup coaching: BMC, execution, brand) align with the instructions and included markdown chains. All actions (asking questions, building BMC, creating a 90-day plan, brand positioning) are coherent with the stated purpose.
Instruction Scope
The SKILL.md explicitly instructs the agent to read and write files under the user's home directory (~/opc-guide/) and to resume conversations by reading existing project files. This file I/O is proportional to a document-oriented coaching skill, but it is behavioral scope the user should be aware of: the agent will access user files in that specific directory and will persist generated documents locally. The instructions do not ask for reading arbitrary system files or credentials.
Install Mechanism
No install steps or external downloads are present (instruction-only). No code is installed or written by the skill itself, which minimizes install-time risk.
Credentials
The skill declares no environment variables, credentials, or config paths. The absence of requested secrets is proportional to its purpose. Note: although no required config paths are declared, the runtime instructions do require filesystem access to ~/opc-guide/ for reading/writing project files.
Persistence & Privilege
always is false and the skill does not request permanent platform-wide privileges. Its persistence is limited to writing and updating files in the user's ~/opc-guide/ directory as part of normal operation, which is appropriate for a document-authoring skill.
Assessment
This skill is a document-focused coaching guide and appears internally consistent. Before enabling it, be aware it will read and write Markdown files in ~/opc-guide/ (create and update project files, and read them when you ask it to resume). If you run agents on a multi-user or sensitive machine, consider restricting file access or reviewing the generated files. There are no network endpoints or credential requests declared — if you see prompts to provide API keys, credentials, or to download/run code, treat that as unexpected and stop. If you want extra assurance, create a dedicated folder (~/opc-guide/) with limited contents and permissions for the skill to use.Like a lobster shell, security has layers — review code before you run it.
latestvk972jdwkfyww5e28xeeq2tqpx583q8pb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.