[Skill Name] - [Short Catchy Title]

[Provide a high-level summary of the skill's purpose, what operations it simplifies, and the benefits of using it.]

Progressive Disclosure & External Resources

[Explicitly state here if this skill is self-contained, or if it relies on external files (e.g., scripts, references, assets). Detail the commands or imports required to run or trigger them without reading the source code.]

• External Resources: [List resources, e.g. "This is a self-contained skill. Do NOT load external files or reference directories." OR list specific scripts and how to execute/import them.]

Freedom Calibration & Constraints

• Constraint Level: [High / Medium / Low]

  • High Rigidity: [Specify exactly what must be followed without exception (e.g., schemas, CLI flags, output formats).]

  • High Freedom: [Specify where the agent has creative/implementation flexibility (e.g., code design, style choices, troubleshooting paths).]

Decision Tree: Choosing the Right Approach

[Include an ASCII diagram or text-based decision tree that helps the agent select the right sub-procedure or tool based on the user's input/scenario.]

User Input/Scenario

 ├─ [Condition A] → [Use Procedure A]

 ├─ [Condition B] → [Use Procedure B]

 └─ [Condition C] → [Fallback/Alternative]

Professional Mindset & Design Principles

1. [Principle 1]: [Describe a mental framework or domain-specific lens to look through.]

2. [Principle 2]: [Describe another key optimization or strategy.]

3. [Principle 3]: [Describe error prevention or sanity-checking strategies.]

---

Step-by-Step Execution Procedure

Step 1: [Phase Name]

• [Instruction in imperative form, e.g., "Analyze the input specifications..."]

• [Instruction, e.g., "Verify that all prerequisites are satisfied..."]

Step 2: [Phase Name]

• [Instruction, e.g., "Execute the primary utility script..."]

• [Instruction, e.g., "Generate the initial output representation..."]

Step 3: [Phase Name]

• [Instruction, e.g., "Perform verification and quality assurance checks..."]

---

Critical Anti-Patterns (NEVER List)

| Anti-Pattern | Description | Alternative / Solution |

| :--- | :--- | :--- |

| NEVER [action to avoid] | [Explain the failure mode or consequence of this action.] | [Provide the correct approach or fallback pattern.] |

| NEVER [action to avoid] | [Explain the failure mode or consequence of this action.] | [Provide the correct approach or fallback pattern.] |

| NEVER [action to avoid] | [Explain the failure mode or consequence of this action.] | [Provide the correct approach or fallback pattern.] |

---

Common Error Scenarios & Fallbacks

Scenario 1: [Error Trigger / Symptom]

• Root Cause: [Explain why this happens.]

• Fallback:

  1. [Step-by-step fallback action 1]

  2. [Step-by-step fallback action 2]

Scenario 2: [Error Trigger / Symptom]

• Root Cause: [Explain why this happens.]

• Fallback:

  1. [Step-by-step fallback action 1]

  2. [Step-by-step fallback action 2]

Memory Sync

After completing key technical findings, architectural decisions, code refactorings, or risk assessments, you MUST trigger the local memory capture.

1. Save the final summary or artifact as a Markdown file in the project directory.
2. Invoke the capture script:

   python3 ~/memory_system/capture_knowledge.py <file_path>
   

3. This ensures that new learnings, policies, and technical snippets are automatically routed to the correct local storage (OKF or ChromaDB).