تشغيل أي مهارة في Manus بنقرة واحدة

openclaw-docs-lookup-morty

النجوم٠

التفرعات٠

آخر تحديث٢٠ فبراير ٢٠٢٦ في ٠٤:٠٢

Look up OpenClaw documentation via web_fetch for config validation and verification. Use when: You need to verify a config key, understand OpenClaw configuration options, or check documentation for Kubernetes-specific settings before making changes. Don't use when: The answer is already in CONFIG.md, AGENTS.md, TOOLS.md in your workspace.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

rajsinghtech

rajsinghtech/openclaw-workspace

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	OpenClaw Docs Lookup (Morty)
description	Look up OpenClaw documentation via web_fetch for config validation and verification. Use when: You need to verify a config key, understand OpenClaw configuration options, or check documentation for Kubernetes-specific settings before making changes. Don't use when: The answer is already in CONFIG.md, AGENTS.md, TOOLS.md in your workspace.
dontUseWhen	["The answer is in your workspace CONFIG.md","You're checking Kuberntes-specific Flux escaping (use CONFIG.md)","General web search needs"]
outputs	Documentation content or config validation results
requires	["web_fetch"]

OpenClaw Docs Lookup for Morty

Augments the main openclaw-docs skill with Kubernetes/Flux-specific awareness.

Routing

Use This Skill When

Verifying config keys that might be specific to your deployment
Checking if a config option requires special handling in Kubernetes
Looking up agent heartbeat configuration options
Understanding subagents.allowAgents syntax
Validating model provider configuration

Don't Use This Skill When

Checking Flux variable escaping ($${VAR}) → see CONFIG.md
Cron job syntax → see CONFIG.md
Subagent spawning patterns → see AGENTS.md
Kubernetes/Flux deployment issues → use flux-debugging skill

Key URLs

Topic	URL
Config reference	https://docs.openclaw.ai/gateway/configuration
Agent runtime	https://docs.openclaw.ai/concepts/agent-runtime
Multi-agent	https://docs.openclaw.ai/concepts/multi-agent
Sessions	https://docs.openclaw.ai/concepts/sessions
Model failover	https://docs.openclaw.ai/concepts/model-failover
TTS	https://docs.openclaw.ai/tts

Kubernetes-Specific Notes

Some documentation assumes local OpenClaw deployment. Key differences in K8s:

Env Var Escaping: Docs show ${VAR} — you must use $${VAR} in git
Config Persistence: Changes to ConfigMap require pod restart (init container limitation)
Workspace Updates: Dockerfile.workspace rebuilds required for workspace changes
Secret Management: Use SOPS + Flux, not plain env files

Config Pattern Quick Reference

// Agent definition
{
  "id": "morty",
  "identity": { "name": "Morty", "emoji": "🔧" },
  "workspace": "/home/node/.openclaw/workspaces/morty",
  "model": { "primary": "aperture/MiniMax-M2.5" },
  "subagents": {
    "model": "aperture/MiniMax-M2.5",
    "allowAgents": ["main"]
  }
}

// Heartbeat configuration
{
  "heartbeat": {
    "every": "30m",
    "model": "aperture/MiniMax-M2.5",
    "target": "discord",
    "activeHours": {
      "start": "08:00",
      "end": "23:00",
      "timezone": "America/New_York"
    }
  }
}

// Model provider example
{
  "models": {
    "mode": "merge",
    "providers": {
      "aperture": {
        "baseUrl": "http://aperture",
        "apiKey": "unused",
        "api": "anthropic-messages"
      }
    }
  }
}

Common Config Mistakes

Mistake	Correction
Wrong `api` type for provider	aperture uses `anthropic-messages`
Missing `subagents.allowAgents`	Add explicit allowlist
Wrong workspace path	Must be `/home/node/.openclaw/workspaces/<id>`
Omitted `model.primary`	Required for each agent

المزيد من هذا المستودع

نفس المستودع

code-review

rajsinghtech/openclaw-workspace

Structured PR review — security scan, correctness, consistency, style. Covers diff analysis, comment posting via gh, and priority-based finding reports. Use when: A PR needs review, someone asks for code feedback, or changes need security/correctness validation before merge. Also use for pre-commit review of your own changes. Don't use when: The issue is a runtime pod failure (use pod-troubleshooting), a Flux reconciliation error (use flux-debugging), or a CI build failure (use ci-diagnosis). Don't use for architecture-level design discussions (use architecture-design instead). Outputs: Review comment posted on the PR via `gh pr review`, or a structured findings report grouped by severity (Critical/High/Medium/Low).

2026-02-200

openspec-workflow

rajsinghtech/openclaw-workspace

Spec-driven development workflow — proposals, requirements, design docs, task breakdowns, and implementation using the OpenSpec framework. Use when: Starting a new feature or change that needs planning, someone says "I want to build X", creating proposals or specs, breaking down requirements into tasks, or transitioning from planning to implementation. Don't use when: Debugging or troubleshooting (use appropriate troubleshooting skill). Don't use for Kubernetes manifest changes (use pr-workflow). Don't use for reviewing existing code (use code-review). Outputs: OpenSpec change folder with proposal.md, specs/, design.md, and tasks.md. Implementation follows directly from tasks.md.

2026-02-200

session-review

rajsinghtech/openclaw-workspace

Analyze agent sessions for tool failures, retry patterns, knowledge gaps, context limits, and config drift. Use when: Running periodic session reviews (cron), investigating agent reliability issues, looking for recurring failure patterns, or identifying workspace improvements from real usage. This is the primary skill for Robert's review cron job. Don't use when: You're making changes to fix issues (use workspace-improvement for that). Don't use for live debugging of a current issue (use the appropriate troubleshooting skill). Don't use for code review of PRs (use code-review). Outputs: Session analysis report with categorized findings (tool failures, retries, knowledge gaps, config drift), severity ratings, and proposed fixes. Written to /tmp/outputs/session-review.md for handoff.

2026-02-200

cluster-context

rajsinghtech/openclaw-workspace

OpenClaw pod architecture, volumes, networking, secrets, and provider configuration reference. Use when: Debugging container, mount, networking, or credential issues. Also use when you need to understand pod structure, check which providers are configured, verify volume mounts, or inspect secrets configuration. Don't use when: Debugging pod crashes (use pod-troubleshooting). Don't use for Flux issues (use flux-debugging). Don't use for deploying changes (use gitops-deploy). This is a reference skill, not a diagnostic workflow. Outputs: Architecture reference information. No artifacts — this skill provides context for other skills to use.

2026-02-200

gitops-deploy

rajsinghtech/openclaw-workspace

End-to-end deployment workflow — commit, CI, Flux reconcile, pod restart, verify. Includes ConfigMap changes, Flux postBuild escaping, and SOPS secret management. Use when: You need to deploy changes to the OpenClaw pod — config updates, workspace changes, image rebuilds, or secret rotations. Also use when someone asks "how do I deploy this?" or "push this change live." Don't use when: You're debugging why a deployment failed (use flux-debugging or pod-troubleshooting). Don't use for changes to kubernetes-manifests repo (Dyson's pr-workflow handles that). Don't use for registry/image inspection (use zot-registry). Outputs: Deployed changes verified in the running pod. Confirmation includes CI status, Flux reconciliation state, pod status, and startup logs.

2026-02-200

sops-credentials

rajsinghtech/openclaw-workspace

Reference for how secrets flow from SOPS-encrypted files in Git through Flux postBuild substitution into Kubernetes Secrets and Pods. Use when: Debugging why a pod can't read a credential, tracing where a secret value comes from, adding a new secret to the pipeline, or understanding the substitution chain (Git → Flux → Secret → Pod). Don't use when: The pod is crashing for non-credential reasons (use pod-troubleshooting). Don't use for Flux reconciliation failures (use flux-debugging). Don't use for OpenClaw-specific config escaping (use config-audit — that covers the $${VAR} pattern). Don't use for CI/CD pipeline issues (use ci-diagnosis). Outputs: Architecture reference. No artifacts — provides context for debugging credential issues across the kubernetes-manifests repo.

2026-02-130

name	OpenClaw Docs Lookup (Morty)
description	Look up OpenClaw documentation via web_fetch for config validation and verification. Use when: You need to verify a config key, understand OpenClaw configuration options, or check documentation for Kubernetes-specific settings before making changes. Don't use when: The answer is already in CONFIG.md, AGENTS.md, TOOLS.md in your workspace.
dontUseWhen	["The answer is in your workspace CONFIG.md","You're checking Kuberntes-specific Flux escaping (use CONFIG.md)","General web search needs"]
outputs	Documentation content or config validation results
requires	["web_fetch"]

OpenClaw Docs Lookup for Morty

Augments the main openclaw-docs skill with Kubernetes/Flux-specific awareness.

Routing

Use This Skill When

Verifying config keys that might be specific to your deployment
Checking if a config option requires special handling in Kubernetes
Looking up agent heartbeat configuration options
Understanding subagents.allowAgents syntax
Validating model provider configuration

Don't Use This Skill When

Checking Flux variable escaping ($${VAR}) → see CONFIG.md
Cron job syntax → see CONFIG.md
Subagent spawning patterns → see AGENTS.md
Kubernetes/Flux deployment issues → use flux-debugging skill

Key URLs

Topic	URL
Config reference	https://docs.openclaw.ai/gateway/configuration
Agent runtime	https://docs.openclaw.ai/concepts/agent-runtime
Multi-agent	https://docs.openclaw.ai/concepts/multi-agent
Sessions	https://docs.openclaw.ai/concepts/sessions
Model failover	https://docs.openclaw.ai/concepts/model-failover
TTS	https://docs.openclaw.ai/tts

Kubernetes-Specific Notes

Some documentation assumes local OpenClaw deployment. Key differences in K8s:

Env Var Escaping: Docs show ${VAR} — you must use $${VAR} in git
Config Persistence: Changes to ConfigMap require pod restart (init container limitation)
Workspace Updates: Dockerfile.workspace rebuilds required for workspace changes
Secret Management: Use SOPS + Flux, not plain env files

Config Pattern Quick Reference

// Agent definition
{
  "id": "morty",
  "identity": { "name": "Morty", "emoji": "🔧" },
  "workspace": "/home/node/.openclaw/workspaces/morty",
  "model": { "primary": "aperture/MiniMax-M2.5" },
  "subagents": {
    "model": "aperture/MiniMax-M2.5",
    "allowAgents": ["main"]
  }
}

// Heartbeat configuration
{
  "heartbeat": {
    "every": "30m",
    "model": "aperture/MiniMax-M2.5",
    "target": "discord",
    "activeHours": {
      "start": "08:00",
      "end": "23:00",
      "timezone": "America/New_York"
    }
  }
}

// Model provider example
{
  "models": {
    "mode": "merge",
    "providers": {
      "aperture": {
        "baseUrl": "http://aperture",
        "apiKey": "unused",
        "api": "anthropic-messages"
      }
    }
  }
}

Common Config Mistakes

Mistake	Correction
Wrong `api` type for provider	aperture uses `anthropic-messages`
Missing `subagents.allowAgents`	Add explicit allowlist
Wrong workspace path	Must be `/home/node/.openclaw/workspaces/<id>`
Omitted `model.primary`	Required for each agent