Lab2startup Growth Maturity

v1.0.0

师生共创成长与成熟阶段指导。当用户完成启动验证,需要产品化、市场拓展、组织建设、技术持续创新时使用。触发词:师生共创成长、产品化、规模化、市场拓展、组织建设、团队扩张、品牌建设、渠道建设

0· 47·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description describe growth/maturity guidance for '师生共创' and the SKILL.md contains detailed, relevant playbooks (productization, market expansion, organization, innovation). There are no unexplained binaries, env vars, or dependencies that would be unrelated to this advisory purpose.
Instruction Scope
The SKILL.md provides step-by-step business guidance, templates, KPIs and output expectations. It does not instruct the agent to read local files, access environment variables, call external endpoints, install or execute code, or collect/transmit sensitive system data. Scope is limited to producing plans and recommendations.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so it writes nothing to disk and installs nothing. That is the lowest-risk install profile.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no disproportionate secret requests or access demands compared to the advisory purpose.
Persistence & Privilege
always:false (no forced inclusion) and default autonomous invocation is allowed by platform norms; the skill does not request elevated or persistent system privileges and does not modify other skills or system configs.
Assessment
This skill appears internally consistent and non-technical: it only contains advisory content and does not request credentials or perform installs. Before using: (1) note the source is unknown—if you need trusted, auditable guidance prefer authored or institution-backed materials; (2) some recommendations reference using university brand (e.g., “清华大学技术团队”)—do not represent or imply endorsements without permission; (3) treat legal, financial, or compliance recommendations as high-level guidance and verify with qualified professionals; (4) if you integrate outputs into operational workflows, validate plans against real-world constraints (contracts, IP, regulatory). Overall technical risk is low, but confirm provenance and legal/brand permissions as needed.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b51hph5yv1empnjnd5yaqzh840r6t

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments