Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Climbing Gym Operations
v1.0.0Operational assistant for independent climbing gyms and bouldering studios — membership management, churn reduction, route-setting coordination, youth progra...
⭐ 0· 48·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description align with the SKILL.md: membership, churn, route-setting, safety, events and revenue work are all described and supported by the instructions and reference docs. However, the capabilities implicitly require integrations (membership DB, billing processor, email/SMS provider, review monitoring, possibly POS and scheduling systems) that are not declared anywhere in the skill metadata.
Instruction Scope
The SKILL.md repeatedly instructs the agent to 'pull' visit, billing, waiver, incident, and enrollment data and to generate outreach (email/SMS) and review-monitoring alerts. It is vague about which data sources, endpoints, or accounts to use and gives the agent broad discretion to fetch and correlate sensitive PII and financial data. That open-ended guidance increases risk because it does not constrain where data comes from or how external communications are sent.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk and no external packages are pulled. This is the lowest-risk install mechanism.
Credentials
No environment variables, credentials, or config paths are declared, yet the described functionality clearly needs access to membership databases, billing/payment processors, email/SMS services, and review APIs. The omission means required secrets/keys and their scope are unspecified — a transparency and least-privilege concern (users wouldn't know which credentials to provide or what the skill will access).
Persistence & Privilege
The skill does not request always:true, does not declare system config modifications, and does not ask to persist settings. Autonomous invocation is permitted (platform default) and appropriate for this class of assistant, but combined with the other concerns it warrants caution.
What to consider before installing
This skill appears to be what it says (an operations assistant for climbing gyms) but it omits critical integration and data-access details. Before installing or enabling it: 1) Ask the publisher for a precise list of required integrations and exact environment variables/credentials (membership DB, billing provider, email/SMS service, review APIs, POS). 2) Require least-privilege API keys (read-only where possible) and consider creating sandbox/test data accounts first. 3) Confirm how PII is stored, processed, and transmitted; insist on TLS endpoints and no logging of full payment data. 4) Restrict the skill's access to only the systems it needs (use service accounts) and enable audit logging. 5) If you allow autonomous invocation, limit its scope initially and monitor actions closely (especially outbound messages and any changes to billing). If the publisher cannot provide clear, explicit integration requirements and a data-flow diagram, treat the skill as high-risk and do not provide production credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk977gbyhtsmjaxqpdrf6nabd3h83xsj5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.