[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FSVTK32N23A2DRY0VA8YA":3,"skill-same:01M75FSVTK32N23A2DRY0VA8YA":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75FSVTK32N23A2DRY0VA8YA","ogt-docs-define",null,"General guide for creating definition documents. Use when you need to define WHAT something IS - concepts, entities, systems, or domains. Routes to specialized sub-skills for specific definition types (business, features, code, marketing, branding, tools).","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Feduardou24\u002Fogt-docs-define\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ogt-docs-define\ndescription: General guide for creating definition documents. Use when you need to define WHAT something IS - concepts, entities, systems, or domains. Routes to specialized sub-skills for specific definition types (business, features, code, marketing, branding, tools).\n---\n\n# OGT Docs - Define\n\nGuide for creating definition documents that establish WHAT things ARE in your system.\n\n## Philosophy\n\n**Definitions are the foundation of shared understanding.**\n\nBefore anyone can implement, market, or discuss something, there must be a clear, agreed-upon definition of what it IS.\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                    THE DEFINITION PRINCIPLE                     │\n├─────────────────────────────────────────────────────────────────┤\n│  A definition answers:                                          │\n│    • WHAT is this thing?                                        │\n│    • WHY does it exist?                                         │\n│    • WHAT are its boundaries? (what it is NOT)                  │\n│    • HOW does it relate to other things?                        │\n│                                                                 │\n│  A definition does NOT specify:                                 │\n│    • HOW to implement it (that's rules\u002F)                        │\n│    • WHAT to do with it (that's todo\u002F)                          │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## When to Use This Skill\n\nUse `ogt-docs-define` when you need to:\n\n- Understand the definitions folder structure\n- Choose the right definition sub-skill\n- Create a definition that doesn't fit specialized categories\n\n**For specific definition types, use:**\n\n| Type                   | Sub-Skill                   | Use When                               |\n| ---------------------- | --------------------------- | -------------------------------------- |\n| Business concepts      | `ogt-docs-define-business`  | Pricing, users, revenue, market        |\n| Product features       | `ogt-docs-define-feature`   | New capabilities, user-facing features |\n| Technical architecture | `ogt-docs-define-code`      | Services, data models, APIs            |\n| Marketing concepts     | `ogt-docs-define-marketing` | Messaging, positioning, audience       |\n| Brand identity         | `ogt-docs-define-branding`  | Visual identity, tone, guidelines      |\n| Developer tools        | `ogt-docs-define-tools`     | CLI, scripts, dev workflows            |\n\n## Folder Structure\n\n```\ndocs\u002Fdefinitions\u002F\n├── business\u002F                   # Business model and operations\n│   ├── pricing_model\u002F\n│   │   ├── definition.md\n│   │   ├── tiers.md\n│   │   ├── limits.md\n│   │   └── .approved_by_founder\n│   ├── user_types\u002F\n│   ├── revenue_model\u002F\n│   └── market_position\u002F\n│\n├── features\u002F                   # Product features\n│   ├── global_search\u002F\n│   │   ├── feature.md\n│   │   ├── mvp.md\n│   │   ├── phase_0.md\n│   │   ├── phase_1.md\n│   │   ├── nice_to_have.md\n│   │   └── .version\n│   ├── user_auth\u002F\n│   └── campaign_manager\u002F\n│\n├── technical\u002F                  # Architecture and systems\n│   ├── service_layer\u002F\n│   │   ├── definition.md\n│   │   ├── contracts.md\n│   │   ├── patterns.md\n│   │   └── .version\n│   ├── data_model\u002F\n│   └── api_design\u002F\n│\n├── domain\u002F                     # Domain-specific concepts\n│   ├── creatures\u002F\n│   ├── abilities\u002F\n│   └── campaigns\u002F\n│\n├── marketing\u002F                  # Marketing and communications\n│   ├── value_proposition\u002F\n│   ├── target_audience\u002F\n│   └── messaging\u002F\n│\n├── branding\u002F                   # Brand identity\n│   ├── visual_identity\u002F\n│   ├── tone_of_voice\u002F\n│   └── brand_guidelines\u002F\n│\n└── tools\u002F                      # Developer tooling\n    ├── cli\u002F\n    ├── scripts\u002F\n    └── workflows\u002F\n```\n\n## The Folder-as-Entity Pattern\n\nEvery definition is a **folder** containing:\n\n```\n{definition_slug}\u002F\n├── {type}.md                   # Primary definition file\n├── {aspect}.md                 # Additional aspects\u002Fdetails\n├── {related}.md                # Related concepts\n└── .{signals}                  # Status and metadata\n```\n\n### Primary File Naming\n\n| Definition Type | Primary File    |\n| --------------- | --------------- |\n| Business        | `definition.md` |\n| Feature         | `feature.md`    |\n| Technical       | `definition.md` |\n| Domain          | `definition.md` |\n| Marketing       | `definition.md` |\n| Branding        | `definition.md` |\n| Tools           | `definition.md` |\n\n## Definition Lifecycle\n\n```mermaid\nflowchart LR\n    subgraph lifecycle [\"Definition Lifecycle\"]\n        D[draft] --> R[review]\n        R --> A[approved]\n        R --> REJ[rejected]\n        REJ --> D\n        A --> DEP[deprecated]\n    end\n\n    style D fill:#fef3c7\n    style R fill:#e0e7ff\n    style A fill:#d1fae5\n    style REJ fill:#fecaca\n    style DEP fill:#e5e7eb\n```\n\n### Draft State\n\nDefinition is being written, not yet ready for review.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n└── .draft                      # Empty signal: still in draft\n```\n\n### Review State\n\nDefinition is complete and awaiting approval.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .ready_for_review           # Empty signal\n└── .review_requested_at        # Timestamp\n```\n\n### Approved State\n\nDefinition is approved and can be referenced\u002Fimplemented.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .approved                   # Empty signal\n├── .approved_by_{name}         # Who approved\n└── .approved_at                # When approved\n```\n\n### Rejected State\n\nDefinition was rejected, needs rework.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .rejected                   # Empty signal\n├── .rejected_reason            # Why rejected\n└── .rejected_at                # When rejected\n```\n\n### Deprecated State\n\nDefinition is outdated, replaced by something else.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .deprecated                 # Empty signal\n├── .deprecated_reason          # Why deprecated\n├── .deprecated_at              # When deprecated\n└── .superseded_by              # What replaces it\n```\n\n---\n\n## Creating a Definition: The Process\n\n```mermaid\nflowchart TD\n    A[Need to define something] --> B{What type?}\n    B -->|Business| C[ogt-docs-define-business]\n    B -->|Feature| D[ogt-docs-define-feature]\n    B -->|Technical| E[ogt-docs-define-code]\n    B -->|Marketing| F[ogt-docs-define-marketing]\n    B -->|Brand| G[ogt-docs-define-branding]\n    B -->|Tools| H[ogt-docs-define-tools]\n    B -->|Other| I[Use this skill]\n\n    I --> J[Ask clarifying questions]\n    J --> K[Draft definition]\n    K --> L[Request review]\n    L --> M{Approved?}\n    M -->|Yes| N[Mark approved]\n    M -->|No| O[Address feedback]\n    O --> K\n```\n\n### Step 1: Ask Clarifying Questions\n\nBefore writing any definition, gather information:\n\n**Core Questions (always ask):**\n\n1. What is the name\u002Fidentifier for this concept?\n2. In one sentence, what IS it?\n3. Why does it need to exist? What problem does it solve?\n4. What is it NOT? (boundaries)\n5. What other concepts does it relate to?\n\n**Context Questions (ask as relevant):** 6. Who are the stakeholders? 7. Are there existing similar concepts? 8. What decisions led to this concept? 9. What are the success criteria?\n\n### Step 2: Draft the Definition\n\nUse the appropriate template based on type (see sub-skills).\n\n**Generic Definition Template:**\n\n```markdown\n# Definition: {Name}\n\n## Overview\n\nOne paragraph explaining what this is and why it exists.\n\n## Core Concept\n\nDetailed explanation of the concept.\n\n### Key Characteristics\n\n- Characteristic 1\n- Characteristic 2\n- Characteristic 3\n\n### Boundaries\n\nWhat this is NOT:\n\n- Not X\n- Not Y\n- Not Z\n\n## Relationships\n\nHow this relates to other concepts.\n\n| Related Concept | Relationship               |\n| --------------- | -------------------------- |\n| Concept A       | Uses\u002FContains\u002FDepends on   |\n| Concept B       | Parallel to\u002FAlternative to |\n\n## Examples\n\nConcrete examples that illustrate the concept.\n\n### Example 1: {Name}\n\nDescription of example.\n\n### Example 2: {Name}\n\nDescription of example.\n\n## Open Questions\n\nUnresolved questions that need future discussion.\n\n- Question 1?\n- Question 2?\n```\n\n### Step 3: Add Signal Files\n\n```bash\n# Create version file\necho '{\"schema\": \"1.0\", \"created\": \"'$(date -Iseconds)'\"}' > .version\n\n# Mark as draft\ntouch .draft\n```\n\n### Step 4: Request Review\n\n```bash\n# Remove draft signal\nrm .draft\n\n# Add review signals\ntouch .ready_for_review\necho \"$(date -Iseconds)\" > .review_requested_at\n```\n\n### Step 5: Handle Review Outcome\n\n**If Approved:**\n\n```bash\nrm .ready_for_review .review_requested_at\ntouch .approved\ntouch .approved_by_{reviewer_name}\necho \"$(date -Iseconds)\" > .approved_at\n```\n\n**If Rejected:**\n\n```bash\nrm .ready_for_review .review_requested_at\ntouch .rejected\necho \"Reason for rejection\" > .rejected_reason\necho \"$(date -Iseconds)\" > .rejected_at\n# Then address feedback and restart from Step 2\n```\n\n---\n\n## Signal Files Reference\n\n### Status Signals (empty files)\n\n| Signal              | Meaning                |\n| ------------------- | ---------------------- |\n| `.draft`            | Still being written    |\n| `.ready_for_review` | Ready for review       |\n| `.approved`         | Approved for use       |\n| `.rejected`         | Rejected, needs rework |\n| `.deprecated`       | No longer current      |\n\n### Attribution Signals (empty files)\n\n| Signal                | Meaning      |\n| --------------------- | ------------ |\n| `.approved_by_{name}` | Who approved |\n| `.created_by_{name}`  | Who created  |\n| `.reviewed_by_{name}` | Who reviewed |\n\n### Content Signals (contain text)\n\n| Signal                 | Content                                     |\n| ---------------------- | ------------------------------------------- |\n| `.version`             | JSON: `{\"schema\": \"1.0\", \"created\": \"...\"}` |\n| `.rejected_reason`     | Why rejected                                |\n| `.deprecated_reason`   | Why deprecated                              |\n| `.superseded_by`       | Path to replacement definition              |\n| `.review_requested_at` | ISO timestamp                               |\n| `.approved_at`         | ISO timestamp                               |\n| `.rejected_at`         | ISO timestamp                               |\n| `.deprecated_at`       | ISO timestamp                               |\n\n---\n\n## Referencing Definitions\n\nWhen other documents reference a definition:\n\n```markdown\nSee [Definition: User Types](docs\u002Fdefinitions\u002Fbusiness\u002Fuser_types\u002F)\nPer the [Service Layer Definition](docs\u002Fdefinitions\u002Ftechnical\u002Fservice_layer\u002F)\n```\n\nWhen code implements a definition, add a comment:\n\n```typescript\n\u002F**\n * Implements: docs\u002Fdefinitions\u002Ftechnical\u002Fservice_layer\u002F\n * @see definition.md for contracts\n *\u002F\nexport class UserService implements IService {\n  \u002F\u002F ...\n}\n```\n\n---\n\n## Common Mistakes\n\n| Mistake                      | Why It's Wrong                             | Correct Approach                        |\n| ---------------------------- | ------------------------------------------ | --------------------------------------- |\n| Mixing definition with rules | Conflates WHAT with HOW                    | Keep definition pure, put HOW in rules\u002F |\n| No boundaries section        | Unclear scope leads to scope creep         | Always define what it is NOT            |\n| Skipping review              | Unvalidated definitions cause misalignment | Always get approval                     |\n| Editing approved definitions | Breaks references                          | Create new version or deprecate         |\n| No relationships section     | Isolated definitions miss connections      | Map relationships explicitly            |\n| Too abstract                 | Can't be implemented                       | Include concrete examples               |\n| Too specific                 | Can't adapt to change                      | Keep at concept level                   |\n\n---\n\n## Quality Checklist\n\nBefore requesting review, verify:\n\n- [ ] Overview explains WHAT and WHY in one paragraph\n- [ ] Core concept is detailed enough to understand\n- [ ] Boundaries clearly state what this is NOT\n- [ ] Relationships map to other definitions\n- [ ] At least 2 concrete examples provided\n- [ ] Open questions listed (if any)\n- [ ] .version file created\n- [ ] .draft signal present (will be removed when requesting review)\n","# OGT Docs - Define\n\nGuide for creating definition documents that establish WHAT things ARE in your system.\n\n## Philosophy\n\n**Definitions are the foundation of shared understanding.**\n\nBefore anyone can implement, market, or discuss something, there must be a clear, agreed-upon definition of what it IS.\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                    THE DEFINITION PRINCIPLE                     │\n├─────────────────────────────────────────────────────────────────┤\n│  A definition answers:                                          │\n│    • WHAT is this thing?                                        │\n│    • WHY does it exist?                                         │\n│    • WHAT are its boundaries? (what it is NOT)                  │\n│    • HOW does it relate to other things?                        │\n│                                                                 │\n│  A definition does NOT specify:                                 │\n│    • HOW to implement it (that's rules\u002F)                        │\n│    • WHAT to do with it (that's todo\u002F)                          │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## When to Use This Skill\n\nUse `ogt-docs-define` when you need to:\n\n- Understand the definitions folder structure\n- Choose the right definition sub-skill\n- Create a definition that doesn't fit specialized categories\n\n**For specific definition types, use:**\n\n| Type                   | Sub-Skill                   | Use When                               |\n| ---------------------- | --------------------------- | -------------------------------------- |\n| Business concepts      | `ogt-docs-define-business`  | Pricing, users, revenue, market        |\n| Product features       | `ogt-docs-define-feature`   | New capabilities, user-facing features |\n| Technical architecture | `ogt-docs-define-code`      | Services, data models, APIs            |\n| Marketing concepts     | `ogt-docs-define-marketing` | Messaging, positioning, audience       |\n| Brand identity         | `ogt-docs-define-branding`  | Visual identity, tone, guidelines      |\n| Developer tools        | `ogt-docs-define-tools`     | CLI, scripts, dev workflows            |\n\n## Folder Structure\n\n```\ndocs\u002Fdefinitions\u002F\n├── business\u002F                   # Business model and operations\n│   ├── pricing_model\u002F\n│   │   ├── definition.md\n│   │   ├── tiers.md\n│   │   ├── limits.md\n│   │   └── .approved_by_founder\n│   ├── user_types\u002F\n│   ├── revenue_model\u002F\n│   └── market_position\u002F\n│\n├── features\u002F                   # Product features\n│   ├── global_search\u002F\n│   │   ├── feature.md\n│   │   ├── mvp.md\n│   │   ├── phase_0.md\n│   │   ├── phase_1.md\n│   │   ├── nice_to_have.md\n│   │   └── .version\n│   ├── user_auth\u002F\n│   └── campaign_manager\u002F\n│\n├── technical\u002F                  # Architecture and systems\n│   ├── service_layer\u002F\n│   │   ├── definition.md\n│   │   ├── contracts.md\n│   │   ├── patterns.md\n│   │   └── .version\n│   ├── data_model\u002F\n│   └── api_design\u002F\n│\n├── domain\u002F                     # Domain-specific concepts\n│   ├── creatures\u002F\n│   ├── abilities\u002F\n│   └── campaigns\u002F\n│\n├── marketing\u002F                  # Marketing and communications\n│   ├── value_proposition\u002F\n│   ├── target_audience\u002F\n│   └── messaging\u002F\n│\n├── branding\u002F                   # Brand identity\n│   ├── visual_identity\u002F\n│   ├── tone_of_voice\u002F\n│   └── brand_guidelines\u002F\n│\n└── tools\u002F                      # Developer tooling\n    ├── cli\u002F\n    ├── scripts\u002F\n    └── workflows\u002F\n```\n\n## The Folder-as-Entity Pattern\n\nEvery definition is a **folder** containing:\n\n```\n{definition_slug}\u002F\n├── {type}.md                   # Primary definition file\n├── {aspect}.md                 # Additional aspects\u002Fdetails\n├── {related}.md                # Related concepts\n└── .{signals}                  # Status and metadata\n```\n\n### Primary File Naming\n\n| Definition Type | Primary File    |\n| --------------- | --------------- |\n| Business        | `definition.md` |\n| Feature         | `feature.md`    |\n| Technical       | `definition.md` |\n| Domain          | `definition.md` |\n| Marketing       | `definition.md` |\n| Branding        | `definition.md` |\n| Tools           | `definition.md` |\n\n## Definition Lifecycle\n\n```mermaid\nflowchart LR\n    subgraph lifecycle [\"Definition Lifecycle\"]\n        D[draft] --> R[review]\n        R --> A[approved]\n        R --> REJ[rejected]\n        REJ --> D\n        A --> DEP[deprecated]\n    end\n\n    style D fill:#fef3c7\n    style R fill:#e0e7ff\n    style A fill:#d1fae5\n    style REJ fill:#fecaca\n    style DEP fill:#e5e7eb\n```\n\n### Draft State\n\nDefinition is being written, not yet ready for review.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n└── .draft                      # Empty signal: still in draft\n```\n\n### Review State\n\nDefinition is complete and awaiting approval.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .ready_for_review           # Empty signal\n└── .review_requested_at        # Timestamp\n```\n\n### Approved State\n\nDefinition is approved and can be referenced\u002Fimplemented.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .approved                   # Empty signal\n├── .approved_by_{name}         # Who approved\n└── .approved_at                # When approved\n```\n\n### Rejected State\n\nDefinition was rejected, needs rework.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .rejected                   # Empty signal\n├── .rejected_reason            # Why rejected\n└── .rejected_at                # When rejected\n```\n\n### Deprecated State\n\nDefinition is outdated, replaced by something else.\n\n```\n{definition_slug}\u002F\n├── definition.md\n├── .version\n├── .deprecated                 # Empty signal\n├── .deprecated_reason          # Why deprecated\n├── .deprecated_at              # When deprecated\n└── .superseded_by              # What replaces it\n```\n\n---\n\n## Creating a Definition: The Process\n\n```mermaid\nflowchart TD\n    A[Need to define something] --> B{What type?}\n    B -->|Business| C[ogt-docs-define-business]\n    B -->|Feature| D[ogt-docs-define-feature]\n    B -->|Technical| E[ogt-docs-define-code]\n    B -->|Marketing| F[ogt-docs-define-marketing]\n    B -->|Brand| G[ogt-docs-define-branding]\n    B -->|Tools| H[ogt-docs-define-tools]\n    B -->|Other| I[Use this skill]\n\n    I --> J[Ask clarifying questions]\n    J --> K[Draft definition]\n    K --> L[Request review]\n    L --> M{Approved?}\n    M -->|Yes| N[Mark approved]\n    M -->|No| O[Address feedback]\n    O --> K\n```\n\n### Step 1: Ask Clarifying Questions\n\nBefore writing any definition, gather information:\n\n**Core Questions (always ask):**\n\n1. What is the name\u002Fidentifier for this concept?\n2. In one sentence, what IS it?\n3. Why does it need to exist? What problem does it solve?\n4. What is it NOT? (boundaries)\n5. What other concepts does it relate to?\n\n**Context Questions (ask as relevant):** 6. Who are the stakeholders? 7. Are there existing similar concepts? 8. What decisions led to this concept? 9. What are the success criteria?\n\n### Step 2: Draft the Definition\n\nUse the appropriate template based on type (see sub-skills).\n\n**Generic Definition Template:**\n\n```markdown\n# Definition: {Name}\n\n## Overview\n\nOne paragraph explaining what this is and why it exists.\n\n## Core Concept\n\nDetailed explanation of the concept.\n\n### Key Characteristics\n\n- Characteristic 1\n- Characteristic 2\n- Characteristic 3\n\n### Boundaries\n\nWhat this is NOT:\n\n- Not X\n- Not Y\n- Not Z\n\n## Relationships\n\nHow this relates to other concepts.\n\n| Related Concept | Relationship               |\n| --------------- | -------------------------- |\n| Concept A       | Uses\u002FContains\u002FDepends on   |\n| Concept B       | Parallel to\u002FAlternative to |\n\n## Examples\n\nConcrete examples that illustrate the concept.\n\n### Example 1: {Name}\n\nDescription of example.\n\n### Example 2: {Name}\n\nDescription of example.\n\n## Open Questions\n\nUnresolved questions that need future discussion.\n\n- Question 1?\n- Question 2?\n```\n\n### Step 3: Add Signal Files\n\n```bash\n# Create version file\necho '{\"schema\": \"1.0\", \"created\": \"'$(date -Iseconds)'\"}' > .version\n\n# Mark as draft\ntouch .draft\n```\n\n### Step 4: Request Review\n\n```bash\n# Remove draft signal\nrm .draft\n\n# Add review signals\ntouch .ready_for_review\necho \"$(date -Iseconds)\" > .review_requested_at\n```\n\n### Step 5: Handle Review Outcome\n\n**If Approved:**\n\n```bash\nrm .ready_for_review .review_requested_at\ntouch .approved\ntouch .approved_by_{reviewer_name}\necho \"$(date -Iseconds)\" > .approved_at\n```\n\n**If Rejected:**\n\n```bash\nrm .ready_for_review .review_requested_at\ntouch .rejected\necho \"Reason for rejection\" > .rejected_reason\necho \"$(date -Iseconds)\" > .rejected_at\n# Then address feedback and restart from Step 2\n```\n\n---\n\n## Signal Files Reference\n\n### Status Signals (empty files)\n\n| Signal              | Meaning                |\n| ------------------- | ---------------------- |\n| `.draft`            | Still being written    |\n| `.ready_for_review` | Ready for review       |\n| `.approved`         | Approved for use       |\n| `.rejected`         | Rejected, needs rework |\n| `.deprecated`       | No longer current      |\n\n### Attribution Signals (empty files)\n\n| Signal                | Meaning      |\n| --------------------- | ------------ |\n| `.approved_by_{name}` | Who approved |\n| `.created_by_{name}`  | Who created  |\n| `.reviewed_by_{name}` | Who reviewed |\n\n### Content Signals (contain text)\n\n| Signal                 | Content                                     |\n| ---------------------- | ------------------------------------------- |\n| `.version`             | JSON: `{\"schema\": \"1.0\", \"created\": \"...\"}` |\n| `.rejected_reason`     | Why rejected                                |\n| `.deprecated_reason`   | Why deprecated                              |\n| `.superseded_by`       | Path to replacement definition              |\n| `.review_requested_at` | ISO timestamp                               |\n| `.approved_at`         | ISO timestamp                               |\n| `.rejected_at`         | ISO timestamp                               |\n| `.deprecated_at`       | ISO timestamp                               |\n\n---\n\n## Referencing Definitions\n\nWhen other documents reference a definition:\n\n```markdown\nSee [Definition: User Types](docs\u002Fdefinitions\u002Fbusiness\u002Fuser_types\u002F)\nPer the [Service Layer Definition](docs\u002Fdefinitions\u002Ftechnical\u002Fservice_layer\u002F)\n```\n\nWhen code implements a definition, add a comment:\n\n```typescript\n\u002F**\n * Implements: docs\u002Fdefinitions\u002Ftechnical\u002Fservice_layer\u002F\n * @see definition.md for contracts\n *\u002F\nexport class UserService implements IService {\n  \u002F\u002F ...\n}\n```\n\n---\n\n## Common Mistakes\n\n| Mistake                      | Why It's Wrong                             | Correct Approach                        |\n| ---------------------------- | ------------------------------------------ | --------------------------------------- |\n| Mixing definition with rules | Conflates WHAT with HOW                    | Keep definition pure, put HOW in rules\u002F |\n| No boundaries section        | Unclear scope leads to scope creep         | Always define what it is NOT            |\n| Skipping review              | Unvalidated definitions cause misalignment | Always get approval                     |\n| Editing approved definitions | Breaks references                          | Create new version or deprecate         |\n| No relationships section     | Isolated definitions miss connections      | Map relationships explicitly            |\n| Too abstract                 | Can't be implemented                       | Include concrete examples               |\n| Too specific                 | Can't adapt to change                      | Keep at concept level                   |\n\n---\n\n## Quality Checklist\n\nBefore requesting review, verify:\n\n- [ ] Overview explains WHAT and WHY in one paragraph\n- [ ] Core concept is detailed enough to understand\n- [ ] Boundaries clearly state what this is NOT\n- [ ] Relationships map to other definitions\n- [ ] At least 2 concrete examples provided\n- [ ] Open questions listed (if any)\n- [ ] .version file created\n- [ ] .draft signal present (will be removed when requesting review)\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Feduardou24\u002Fogt-docs-define",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill ogt-docs-define",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill ogt-docs-define",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill ogt-docs-define","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Feduardou24\u002Fogt-docs-define\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]