Subskill Generation Rule

Define and enforce project orgnization rules for generating subskills. put generated recommendation outputs under data/, place new feature scripts under subskills/<feature>/, and optionally add SKILL.md inside each feature folder to keep main skill root clean.

Audits

Pass

ClawScanPass

Agentic behavior and permission review.

Static analysisPass

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install subskill-generation-rule

Subskill Generate Rule

Apply these rules for future updates:

Store newly generated recommendation/result artifacts in data/.
Place newly generated code scripts in subskills/<feature>/.
Use one folder per feature under subskills/.
Add SKILL.md inside the feature folder when behavior/usage needs instructions.
Avoid adding one-off scripts and generated files in the main skill root.

Recommended layout:

<skill>/
  SKILL.md
  config.json
  data/
  subskills/
    <feature-a>/
      SKILL.md
      *.py
    <feature-b>/
      SKILL.md
      *.py

When to Use

Creating new subskills
Organizing existing features
Enforcing file placement conventions
Keeping skill root clean