QA Report — Simple Tier Skill Changes¶
Reviewer: Quinn, Lead QA Engineer
Date: 2026-03-20
Scope: Negative trigger additions and stale content fixes across 9 workspace skills
Summary¶
| Skill | Result |
|---|---|
| cost-estimation | ✅ PASS |
| memory-manager | ✅ PASS |
| openclaw-prime | ✅ PASS |
| project-pipeline | ⚠️ PASS (minor note) |
| qa-validation | ✅ PASS |
| frontend-design | ✅ PASS |
| vv-dashboard-design | ✅ PASS |
| vv-sigint | ✅ PASS |
| service-management | ✅ PASS |
Overall: 9/9 PASS (1 with minor advisory, no blockers)
Individual Skill Reviews¶
1. cost-estimation¶
File: /Users/viverevitalis/.openclaw/workspace/skills/cost-estimation/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for billing disputes or exact invoicing — this produces estimates only, not billing-grade numbers."
- [x] Negative trigger makes sense — correctly scopes the skill to estimation only, not authoritative billing data
- [x] No conflict with skill purpose — the skill is for estimates; the trigger correctly excludes billing-grade use
- [x] Frontmatter YAML valid — proper --- delimiters, single-line description, no formatting issues
- [x] Description accurately reflects what the skill does and when to use it
Notes: Clean and well-scoped. No issues.
2. memory-manager¶
File: /Users/viverevitalis/.openclaw/workspace/skills/memory-manager/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for session-to-session conversation continuity — that is handled by the AGENTS.md startup routine."
- [x] Negative trigger makes sense — important distinction between memory lifecycle management vs. session continuity flow
- [x] No conflict with skill purpose — memory-manager governs capture/store/prune/consolidate; session startup routine is a separate concern handled by AGENTS.md
- [x] Frontmatter YAML valid — uses block scalar > for multi-line description, proper --- delimiters
- [x] Description accurately covers all 5 use cases + cron + write-back pipeline
Notes: Multi-line YAML block scalar format is correct and well-formed. No issues.
3. openclaw-prime¶
File: /Users/viverevitalis/.openclaw/workspace/skills/openclaw-prime/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for OpenClaw feature requests or bug reports — file those on GitHub."
- [x] Negative trigger makes sense — this skill is for operator/admin tasks, not upstream software issues
- [x] No conflict with skill purpose — prime is for priming context for live config/ops work; routing bugs to GitHub is a valid exclusion
- [x] Frontmatter YAML valid — quoted single-line description, proper delimiters
- [x] Description accurately covers all use cases (admin questions, config changes, debugging, deployments, operational decisions)
Notes: Local environment block in the body (Step 4) reflects current setup correctly (claude-opus-4-6, Telegram channel, Mac mini). No stale content detected.
4. project-pipeline¶
File: /Users/viverevitalis/.openclaw/workspace/skills/project-pipeline/SKILL.md
Result: ✅ PASS (with minor advisory)
Checklist:
- [x] Negative trigger present: "Do NOT use for existing initiative status tracking — that is managed in initiative STATUS.md files."
- [x] Negative trigger makes sense — pipeline is for new/incoming ideas, not maintaining existing initiative state
- [x] No conflict with skill purpose — clear and accurate exclusion
- [x] Frontmatter YAML valid — proper --- delimiters, single-line description
- [x] Description accurately reflects brainstorming, evaluation, routing, and deferral use cases
Advisory (non-blocking): The body references absolute hardcoded paths (/Users/viverevitalis/.openclaw/workspace/PROJECT_EVALUATION_TEMPLATE.md and PROJECT_PIPELINE.md). These work in the current environment but are brittle if the workspace path ever changes. Recommend converting to workspace-relative paths (e.g., PROJECT_EVALUATION_TEMPLATE.md) in a future pass. Not a blocker for this release.
5. qa-validation¶
File: /Users/viverevitalis/.openclaw/workspace/skills/qa-validation/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for research validation or business analysis — this is for code and build QA only."
- [x] Negative trigger makes sense — correctly excludes non-code validation contexts that might otherwise trigger this skill
- [x] No conflict with skill purpose — QA validation is exclusively for build/system/UI verification
- [x] Frontmatter YAML valid — proper delimiters, clean single-line description
- [x] Description accurately describes the SOP for Quinn and Jules pre-completion verification
Notes: Mission Control dashboard QA section (Section 3) is substantive and appropriate. No stale content detected.
6. frontend-design¶
File: /Users/viverevitalis/.openclaw/workspace/skills/frontend-design/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for Mission Control dashboard work — use vv-dashboard-design instead."
- [x] Negative trigger makes sense — critical disambiguation between general web work and MC-specific work with its own design system
- [x] No conflict with skill purpose — frontend-design is for generic/external web UIs; the exclusion correctly routes MC work elsewhere
- [x] Frontmatter YAML valid — proper --- delimiters, single-line description
- [x] Description accurately describes what the skill does (distinctive, production-grade frontend interfaces) and when to use it
Notes: The cross-reference to vv-dashboard-design in the negative trigger is bidirectional and consistent with vv-dashboard-design's negative trigger. Good pairing.
7. vv-dashboard-design¶
File: /Users/viverevitalis/.openclaw/workspace/skills/vv-dashboard-design/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for non-MC web projects — use frontend-design for general web work."
- [x] Negative trigger makes sense — vv-dashboard-design is a constrained design system for Mission Control only
- [x] No conflict with skill purpose — the skill governs MC-specific design tokens, component patterns, and brand application
- [x] Frontmatter YAML valid — uses block scalar > format correctly, proper --- delimiters
- [x] Description accurately covers all areas: tokens, components, accessibility, data viz, VV brand, and MC-specific coding agent guidance
Notes: Bidirectional cross-reference with frontend-design is intact and correct. The body content is comprehensive and current (Next.js 15, Tailwind, framer-motion). No stale content detected.
8. vv-sigint¶
File: /Users/viverevitalis/.openclaw/workspace/skills/vv-sigint/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for internal project status or team updates — this is for external signal gathering only."
- [x] Negative trigger makes sense — SigInt is explicitly about external sources; internal tracking belongs elsewhere
- [x] No conflict with skill purpose — SigInt is for external signal scanning, curation, and delivery
- [x] Frontmatter YAML valid — block scalar > format, proper --- delimiters
- [x] Description accurately describes Atlas + agent scanning, column population, curation, digests, source watch lists, and scan scheduling
Stale Content Fix Verification:
- [x] CONFIRMED: The ## Cron Schedule section no longer contains a hardcoded cron time or specific schedule values. It now reads: "Scan and digest schedules are managed by OpenClaw cron jobs. Check cron list for current times and delivery settings. This skill defines what happens during a scan — the cron jobs define when."
- This is the correct fix — the stale hardcoded schedule has been replaced with a dynamic reference to the live cron configuration.
Notes: Stale cron fix is correct and complete. No issues.
9. service-management¶
File: /Users/viverevitalis/.openclaw/workspace/skills/service-management/SKILL.md
Result: ✅ PASS
Checklist:
- [x] Negative trigger present: "Do NOT use for cloud-deployed services or CI/CD pipelines — this is for local Mac mini operations only."
- [x] Negative trigger makes sense — clearly scopes the skill to local macOS only, preventing misapplication to cloud/CI contexts
- [x] No conflict with skill purpose — the skill is explicitly about local Mac mini service lifecycle management
- [x] Frontmatter YAML valid — proper --- delimiters, single-line description
- [x] Description accurately covers launching, maintaining, verifying long-running services + project scaffolding
Notes: Body content is accurate for the local environment. lsof caveat in Section 4 is a valid and useful operational note. No stale content detected.
Findings Summary¶
Issues Requiring Action¶
None. All skills pass.
Advisories (Non-Blocking)¶
- project-pipeline — Absolute hardcoded workspace paths in skill body (
/Users/viverevitalis/.openclaw/workspace/...). Consider converting to relative paths in a future pass for portability.
Notable Quality Observations¶
- The bidirectional negative trigger pairing between
frontend-design↔vv-dashboard-designis well-executed — each skill correctly routes to the other. - The vv-sigint stale cron fix is clean and correct — dynamic reference to
cron listis the right pattern. - YAML frontmatter is consistently valid across all 9 skills. No broken delimiters or malformed block scalars detected.
- Negative triggers are appropriately scoped — none overly broad, none missing meaningful exclusions.
QA completed by Quinn — 2026-03-20