@trespies-source/dojo-genesis-plugin 1.0.0

package/skills/skill-audit-upgrade/SKILL.md

@@ -0,0 +1,427 @@
+---
+name: skill-audit-upgrade
+description: Audit all skills in a repository to assess completeness and upgrade incomplete skills to quality standards. Use when you've created many new skills, before a major release, to maintain ecosystem consistency, or to improve skill usability. Trigger phrases: 'audit all the skills', 'upgrade skills to A+ standard', 'check skill quality and completeness', 'are the skills production-ready', 'improve the skills ecosystem'.
+---
+
+> **OpenClaw Integration:** This skill is invoked by the Dojo Genesis plugin via `/dojo run skill-audit-upgrade`.
+> The agent receives project context automatically via the `before_agent_start` hook.
+> Use `dojo_get_context` for full state, `dojo_save_artifact` to persist outputs,
+> and `dojo_update_state` to record phase transitions and decisions.
+
+# Skill Audit and Upgrade
+
+**Version:** 1.0  
+**Created:** 2026-02-07  
+**Author:** Manus AI  
+**Purpose:** To provide a systematic, repeatable process for auditing all skills in a repository, identifying gaps, and upgrading incomplete skills to A+ standard.
+
+---
+
+## I. The Philosophy: Ecosystem Health Through Systematic Audits
+
+A skills ecosystem, like any knowledge base, can degrade over time. New skills are created with high standards, but older skills may lack structure, examples, or ecosystem connections. Without regular audits, the quality becomes inconsistent, making the ecosystem harder to use and maintain.
+
+This skill is about **proactive maintenance**. By systematically auditing all skills against clear quality criteria, we can identify gaps early, prioritize upgrades, and ensure the entire ecosystem remains healthy and production-ready.
+
+**The core principle:** Maintenance is not just fixing what's broken—it's keeping what works working well.
+
+---
+
+## II. When to Use This Skill
+
+- **Quarterly maintenance schedule** (every 3 months)
+- **After creating 5+ new skills** (to check for consistency)
+- **When a skill is reported as confusing or incomplete**
+- **Before a major release** (to ensure all skills are production-ready)
+- **When onboarding a new contributor** (to assess current state)
+- **After a major refactor** (e.g., skill renames, terminology changes)
+
+---
+
+## III. The Workflow
+
+This is a 5-step workflow for auditing and upgrading skills.
+
+### Step 1: List All Skills and Create Audit Framework
+
+**Goal:** Establish a systematic approach to auditing skills.
+
+**Actions:**
+1. List all skills in the repository:
+   ```bash
+   cd /path/to/repository/skills && ls -d */ | sed 's|/||' | sort
+   ```
+2. Create audit framework document defining:
+   - **Quality criteria:** Required, recommended, and optional sections
+   - **Assessment scale:** A+, A, B, C, D (with clear definitions)
+   - **Audit process:** Step-by-step instructions
+   - **Upgrade priority criteria:** High, medium, low
+
+**Outputs:**
+- List of all skills to audit
+- `skills_audit_framework.md` document
+
+**Quality Criteria Example:**
+
+**Required Sections:**
+- Philosophy (I.)
+- When to Use (II.)
+- Workflow (III.)
+- Best Practices (IV.)
+- Quality Checklist (V.)
+
+**Recommended Sections:**
+- Example (VI.)
+- Common Pitfalls (VII.)
+- Related Skills (VIII.)
+
+**Optional Sections:**
+- Skill Metadata (IX.)
+
+**Assessment Scale:**
+- **A+:** All required + all recommended sections
+- **A:** All required sections, missing some recommended
+- **B:** Missing 1-2 required sections
+- **C:** Missing 3+ required sections
+- **D:** Incomplete or unusable
+
+---
+
+### Step 2: Read and Assess Each Skill Against Quality Criteria
+
+**Goal:** Systematically evaluate each skill's completeness.
+
+**Actions:**
+1. Check line counts for all skills to identify obviously incomplete ones:
+   ```bash
+   for dir in */; do echo "$dir: $(wc -l < "$dir/SKILL.md") lines"; done
+   ```
+2. Use grep to extract section headers from each skill:
+   ```bash
+   for skill in */SKILL.md; do echo "=== $skill ==="; grep -E "^## [IVX]+\." "$skill"; done
+   ```
+3. For each skill, assess against quality criteria:
+   - Check for required sections
+   - Check for recommended sections
+   - Check for proper structure (section numbering)
+4. Assign grades (A+, A, B, C, D) based on completeness
+
+**Outputs:**
+- Assessment for each skill
+- Gaps identified for each skill
+- Grades assigned
+
+**Tips:**
+- Use grep with regex to extract only numbered sections: `grep -E "^## [IVX]+\."`
+- Check line counts first to identify obviously incomplete skills
+- If a skill has <50 lines, it's likely incomplete
+
+---
+
+### Step 3: Identify Skills Needing Upgrade and Prioritize
+
+**Goal:** Create a prioritized list of skills to upgrade.
+
+**Actions:**
+1. Categorize skills by grade:
+   - Count A+ skills
+   - Count A skills
+   - Count B/C/D skills
+2. Define upgrade priorities:
+   - **High Priority:** D or C skills (critically incomplete)
+   - **Medium Priority:** B skills (structural fixes needed)
+   - **Low Priority:** A skills (enhancement, not blocking)
+3. Estimate time for each upgrade:
+   - Structural fixes: ~30-45 minutes per skill
+   - Adding examples/pitfalls: ~15-30 minutes per skill
+4. Create upgrade plan with prioritized list
+
+**Outputs:**
+- `skills_audit_report.md` with complete assessment
+- Prioritized upgrade list
+- Time estimates for upgrades
+
+**Upgrade Priority Criteria:**
+- **High:** Skill is blocking workflows or unusable
+- **Medium:** Skill is functional but lacks structure/consistency
+- **Low:** Skill is functional, enhancement would be nice-to-have
+
+---
+
+### Step 4: Upgrade Incomplete Skills
+
+**Goal:** Bring incomplete skills to A+ standard.
+
+**Actions:**
+1. For each skill to upgrade:
+   - Read current content
+   - Add missing required sections
+   - Add section numbering (I., II., III., etc.)
+   - Add Example section (use real project examples)
+   - Add Common Pitfalls section (5 pitfalls with solutions)
+   - Add Related Skills section (5 complementary skills)
+   - Add Skill Metadata section (token savings, maintenance schedule)
+   - Version bump (e.g., v1.0 → v1.1)
+
+2. For structural fixes:
+   - Ensure consistent section numbering
+   - Ensure all required sections present
+   - Ensure proper frontmatter (name, description)
+
+3. For content enhancements:
+   - Add concrete examples from real projects
+   - Structure examples as: Problem → Process → Outcome
+   - Make pitfalls specific with before/after examples
+   - Link to complementary skills in the ecosystem
+
+**Outputs:**
+- Upgraded skills at A or A+ standard
+- Version bumps documented
+
+**Best Practices:**
+- Use real project examples for credibility
+- Structure examples consistently
+- Make pitfalls actionable (not just warnings)
+- Create ecosystem connections through related skills
+
+---
+
+### Step 5: Commit All Upgrades and Deliver Final Audit Report
+
+**Goal:** Finalize the work and document the results.
+
+**Actions:**
+1. Copy audit documents to appropriate directory (e.g., `thinking/`)
+2. Stage all changes: `git add skills/ thinking/`
+3. Commit with comprehensive message documenting:
+   - Number of skills upgraded
+   - Changes made (section numbering, examples, pitfalls, etc.)
+   - Grade improvements (e.g., B+ → A+)
+   - Audit results (before/after percentages)
+4. Push to remote: `git push origin main`
+5. Create final summary document
+
+**Outputs:**
+- Committed and pushed changes
+- Final audit summary document
+- Updated skills ecosystem
+
+**Commit Message Template:**
+```
+Upgrade X skills to A+ standard and complete skills audit
+
+SKILLS UPGRADED (vX.Y → vX.Z):
+
+1. skill-name-1
+   - Added [changes]
+   - Grade: B+ → A+
+
+2. skill-name-2
+   - Added [changes]
+   - Grade: A → A+
+
+AUDIT RESULTS:
+
+- A+ Skills: X → Y (Z%)
+- A Skills: X → Y (Z%)
+- B+ Skills: X → Y (Z%)
+
+[Summary of ecosystem health]
+```
+
+---
+
+## IV. Best Practices
+
+### 1. Define Clear Quality Criteria Upfront
+
+**Why:** Makes the audit objective and actionable.
+
+**How:** Create a framework document before starting the audit.
+
+---
+
+### 2. Use Automation for Initial Assessment
+
+**Why:** Manually reading 10+ skills is time-consuming.
+
+**How:** Use shell commands (grep, wc) to quickly identify gaps.
+
+---
+
+### 3. Focus on Structural Issues First
+
+**Why:** Structure is easier to fix than content, and has high impact.
+
+**How:** Prioritize adding section numbering and missing required sections.
+
+---
+
+### 4. Use Real Project Examples
+
+**Why:** Concrete examples make skills immediately actionable.
+
+**How:** Reference actual project work (e.g., "Dojo Genesis v0.0.31").
+
+---
+
+### 5. Create Ecosystem Connections
+
+**Why:** Skills are not isolated—they're part of an ecosystem.
+
+**How:** Add Related Skills sections to every skill.
+
+---
+
+### 6. Document the Audit Process
+
+**Why:** Creates a historical record and enables future audits.
+
+**How:** Create audit framework and audit report documents.
+
+---
+
+### 7. Celebrate the Work
+
+**Why:** Maintenance is often invisible work. Make it visible.
+
+**How:** Create a comprehensive summary document highlighting improvements.
+
+---
+
+## V. Quality Checklist
+
+Before completing the audit, ensure you can answer "yes" to all of the following questions:
+
+- [ ] Have you listed all skills in the repository?
+- [ ] Have you created an audit framework with clear quality criteria?
+- [ ] Have you assessed each skill against the quality criteria?
+- [ ] Have you assigned grades (A+, A, B, C, D) to all skills?
+- [ ] Have you identified and prioritized skills needing upgrade?
+- [ ] Have you upgraded all high-priority skills?
+- [ ] Have you committed all changes with comprehensive messages?
+- [ ] Have you created a final audit report documenting the results?
+- [ ] Are all skills now at A or A+ standard (or have a plan to get there)?
+
+---
+
+## VI. Example: Dojo Genesis Skills Audit (February 7, 2026)
+
+**The Problem:** After creating 5 new skills in one day, we needed to audit the entire skills ecosystem to ensure consistency and completeness.
+
+**The Process:**
+
+1. **Listed all skills:** 11 skills in dojo-genesis/skills directory
+2. **Created audit framework:** Defined quality criteria and assessment scale
+3. **Assessed each skill:**
+   - A+ Skills: 4/11 (36%)
+   - A Skills: 5/11 (45%)
+   - B+ Skills: 2/11 (18%)
+4. **Identified gaps:**
+   - 2 skills lacking section numbering (I., II., III.)
+   - 2 skills missing Example, Common Pitfalls, Related Skills sections
+5. **Upgraded 2 skills:**
+   - multi-surface-strategy (v1.0 → v1.1)
+   - product-positioning (v1.0 → v1.1)
+   - Added section numbering, examples, pitfalls, related skills
+6. **Committed and documented:**
+   - Commit `eeca836` pushed to dojo-genesis
+   - Final audit report created
+
+**The Outcome:**
+- A+ Skills: 4 → 6 (55%)
+- A Skills: 5 (45%)
+- B+ Skills: 2 → 0 (0%)
+- 100% of skills now at A or A+ standard
+
+**Time Investment:** ~1.5 hours  
+**Return:** Healthy, production-ready skills ecosystem
+
+**Key Insight:** Most skills were already functional (A-grade). Only 2 needed structural fixes. Regular audits prevent degradation.
+
+---
+
+## VII. Common Pitfalls to Avoid
+
+### Pitfall 1: No Clear Quality Criteria
+
+**Problem:** Without clear criteria, the audit becomes subjective and inconsistent.
+
+**Solution:** Create an audit framework document before starting the audit.
+
+---
+
+### Pitfall 2: Trying to Read Every Skill Manually
+
+**Problem:** Manually reading 10+ skills is time-consuming and error-prone.
+
+**Solution:** Use shell commands (grep, wc) to quickly identify gaps.
+
+---
+
+### Pitfall 3: Upgrading Everything at Once
+
+**Problem:** Trying to upgrade all skills to A+ standard is overwhelming.
+
+**Solution:** Prioritize. Focus on high-priority (blocking) skills first.
+
+---
+
+### Pitfall 4: Skipping the Audit Report
+
+**Problem:** Without documentation, the audit work is invisible and not repeatable.
+
+**Solution:** Create audit framework and audit report documents.
+
+---
+
+### Pitfall 5: Not Using Real Examples
+
+**Problem:** Generic examples don't help users understand how to apply the skill.
+
+**Solution:** Use concrete examples from real projects (e.g., "Dojo Genesis v0.0.31").
+
+---
+
+## VIII. Related Skills
+
+- **`skill-maintenance`** - Use this for ongoing maintenance of individual skills
+- **`process-extraction`** - Use this to create new skills from processes
+- **`compression-ritual`** - Use this to preserve learnings before/after audits
+- **`strategic-to-tactical-workflow`** - The complete workflow that these skills support
+- **`release-specification`** - Example of an A+ skill with all recommended sections
+
+---
+
+## IX. Skill Metadata
+
+**Token Savings:** ~10,000-15,000 tokens per audit (by using systematic process)  
+**Quality Impact:** Ensures consistent, high-quality skills ecosystem  
+**Maintenance:** Update when quality criteria evolve or new section types emerge
+
+**When to Update This Skill:**
+- After completing 2-3 audits (to incorporate new patterns)
+- When quality criteria change (e.g., new required sections)
+- When new assessment scales or tools become available
+
+**Recommended Audit Frequency:**
+- Quarterly (every 3 months)
+- After creating 5+ new skills
+- Before major releases
+
+---
+
+**Last Updated:** 2026-02-07  
+**Maintained By:** Manus AI  
+**Status:** Active
+---
+
+## OpenClaw Tool Integration
+
+When running inside the Dojo Genesis plugin:
+
+1. **Start** by calling `dojo_get_context` to retrieve full project state, history, and artifacts
+2. **During** the skill, follow the workflow steps documented above
+3. **Save** outputs using `dojo_save_artifact` with the `artifacts` output directory
+4. **Update** project state by calling `dojo_update_state` to record skill completion and any phase transitions
+

package/skills/skill-audit-upgrade/claw.json

@@ -0,0 +1,12 @@
+{
+  "name": "dojo-genesis-plugin-skill-audit-upgrade",
+  "version": "1.0.0",
+  "description": "Audit and upgrade skills to quality standards",
+  "author": "dojo-genesis",
+  "license": "MIT",
+  "permissions": [],
+  "entry": "SKILL.md",
+  "tags": ["dojo-genesis", "orchestration", "forge", "skills"],
+  "models": ["claude-*", "gpt-*", "gemini-*"],
+  "minOpenClawVersion": "2026.1.0"
+}

package/skills/skill-creation/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.