ClawHub Skill Compliance Checklist#

Purpose: Ensure skills have complete metadata, transparent dependencies, and clear security scope before publishing.

Target: Legitimate skill authors seeking clean publishing status.

---

Pre-flight Checklist#

1. Metadata Completeness#

CheckFixMissing name?Add: name: skill-nameVague description?Add triggers: "Use when: X, Y"Missing exclusions?Add: "NOT for: simple X"

---

2. Dependency Transparency#

CheckFixReferences external skill?Declare: dependencies.skillsUses specific tools?Declare: dependencies.toolsForced skill loading?Make optional

Transparency principle: All dependencies should be declared in frontmatter.

---

3. Environment Variables#

CheckFixUses API keys?Declare: env.optionalHardcoded secrets?Use annotated placeholder

Placeholder format: <your-api-key> (not actual values)

---

4. Security Scope#

CheckFixMissing section?Add Security ScopeUnclear capabilities?List: does / does NOT

Template:

markdown

## Security Scope
**What this skill does**: [list]
**What this skill does NOT**: [list]

---

5. Instruction Consistency#

CheckFixHeader contradicts examples?Align bothShows excluded behavior?Remove from examples

---

6. Platform Commands#

CheckFixPlatform-specific command?Mark as optional

---

7. Content Simplicity#

CheckFixComplex examples?Simplify for clarityRedundant details?Consolidate into tables

Simplicity principle: Clear, concise content is easier for scanners to analyze accurately.

---

8. Safe Package References#

CheckFixUsing remote execution?Prefer global installUsing npx -y?Remove (no verification bypass)

Safe pattern: Verify package, install globally, use binary name.

---

Transparency Guidelines#

When simplifying content:

1. Use annotated placeholders: <your-api-key>, <project-url>
2. Keep necessary context: Security scope, dependencies
3. Don't remove security information: Keep what reviewers need
4. Log all changes: Track what was simplified and why

Goal: Accurate scanner analysis, not hiding content.

---

Security Warning#

This skill is for legitimate skill authors only.

Do NOT use this checklist:

• To publish malicious content
• To hide harmful behavior
• To bypass legitimate security reviews

Misuse: Using these guidelines for malicious skills violates trust and may result in account suspension.

---

Issue Coverage#

CategoryCoverageMetadata completeness100%Dependency transparency100%Security scope100%Instruction consistency90%Safe package references100%

---

Compliance Checklist v2.2 - 2026-04-05