Gingiris B2b Growth
v2.0.0B2B SaaS Growth Playbook — Product-Led Growth (PLG) & Sales-Led Growth (SLG) strategies. Complete guide from PMF validation to $10M ARR. Real case studies: H...
⭐ 0· 407·1 current·1 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 skill name/description (B2B growth playbook) matches the provided files (guides, templates, metrics, SEO/GEO advice, contract/SOW/MSA templates). There are no unrelated requirements (no cloud creds, no binaries) that would contradict the stated purpose.
Instruction Scope
SKILL.md and the referenced files are documentation and templates for growth, customer research, partner programs, contracts, and metrics. The instructions do not ask the agent to read system files, environment variables, or transmit data to hidden endpoints; links point to GitHub and the author's website/contacts, which is expected for a docs bundle.
Install Mechanism
No install spec, no code files that would be executed, and no downloads. This is the lowest-risk form (instruction-only documentation) and nothing is written to disk by an installer.
Credentials
The skill declares no required environment variables, credentials, or config paths. The content references third‑party services/tools (e.g., Mixpanel, PartnerStack) only as recommendations, not as required credentials — proportional to the content.
Persistence & Privilege
always is false, the skill is user-invocable and can be invoked autonomously (default), and it does not request elevated persistence or access to other skills/config. No privileged behaviors are present.
Scan Findings in Context
[regex_scan_no_findings] expected: The static scanner had nothing to analyze because this is instruction-only documentation; absence of findings is expected for a docs-only skill.
Assessment
This skill is a documentation bundle/ playbook — it appears internally consistent and contains templates (contracts, SOWs) and operational advice. Consider: 1) Verify the author and sources if you plan to use contract templates or legal text in production (have a lawyer review). 2) Many templates assume collecting user data (emails, interview recordings); ensure you obtain consent and follow privacy laws (GDPR/CCPA) before using them. 3) Links point to external sites (GitHub, gingiris.com) and public contact info; treat those as ordinary references and avoid pasting sensitive credentials into examples. If you need higher assurance about authorship or legal compliance, request publisher provenance or a signed license from the maintainer.Like a lobster shell, security has layers — review code before you run it.
latestvk979ntmfh7f3ahkdf1nyxymbrs83hvpr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.