Editorial Policy

1. Evidence standard

Technical claims are based on reproducible steps, observed command outcomes, and clear environment assumptions.

• We prefer command-level proof over generalized best-practice language.
• When evidence is partial, we mark the scope and avoid over-claiming results.
• We separate source-derived facts from editorial interpretation.

2. Security and safety

We prioritize least privilege, explicit permission boundaries, and rollback guidance. Risky operations are labeled with pre-checks and failure criteria.

• Dangerous or high-impact commands include explicit guardrails.
• Permission-sensitive workflows include pre-run checks and rollback triggers.
• Security caveats are kept in-page, not hidden in external notes.

3. Update cadence

Articles are reviewed when major runtime behavior changes are detected. Material changes are reflected in update logs and correction notes.

Priority is assigned by user impact: security-impacting fixes first, broken install paths second, and quality improvements after operational issues are resolved.

4. Independence

OpenClawSkill.cc is an independent community project. We are not affiliated with the official OpenClaw project.

5. Attribution and Source Integrity

For verified skill pages, source fields are kept separate from editorial analysis. We preserve source descriptions as provided and label our own verification notes independently to avoid attribution ambiguity.

6. Reader Feedback and Escalation

Readers can report inaccuracies by email. Reports are triaged, reproduced when possible, and resolved through either direct page correction or an explicit limitation note when reproduction is not currently possible.