OpenClaw Official Skills Collection
53 production-tested bundled OpenClaw skills spanning Obsidian notes, Google Workspace (gog), GitHub, Slack, smart home, CI/CD monitoring, social, and moreâreference implementations for skill architecture.
Overview
OpenClaw Official Skills Collection is a Claude agent catalogued in LimeDock Directories for teams working across operations, engineering, marketing, other. It is tagged for saas, agency, other contexts. 53 production-tested bundled OpenClaw skills spanning Obsidian notes, Google Workspace (gog), GitHub, Slack, smart home, CI/CD monitoring, social, and moreâreference implementations for skill architecture. Use this page as the operational brief: install path, how to invoke it, copy-paste prompts, prerequisites, and concrete use cases so your team can adopt it without re-reading every roundup article.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Agents are a starting point. LimeDock turns the workflow into production automation your SaaS team owns — not another prompt library.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Install/use via OpenClaw (natural language skill URL install or ClawHub CLI). Study bundled skills as templates before building your own.
Generic install paths
CLI
npx skills add https://github.com/openclaw/openclaw**Claude Code plugins** (when published as a marketplace skill)
/plugin marketplace add <org/repo>
/plugin install <skill>@<marketplace>**Manual** — copy the skill folder into `~/.claude/skills/openclaw-official-skills/` or your project `.claude/skills/`.
Always review `SKILL.md` and bundled scripts before enabling.
How to use it
In OpenClaw, paste skill URLs or `clawhub install <slug>`; invoke by describing daily workflows the bundle covers.
**Suggested workflow** 1. Install and enable the agent. 2. Open the target project (or Claude.ai chat) with enough product context. 3. Invoke with a clear goal, constraints, and success criteria. 4. Review the first output against your standards; refine with follow-ups. 5. Save winning prompts / outputs into your team playbook.
If Claude does not auto-select it, mention the agent by name: “Use the OpenClaw Official Skills Collection agent…”
Example prompts
- “Use the OpenClaw Official Skills Collection agent for this task: Obsidian note workflows”
- “Walk me through how OpenClaw Official Skills Collection would approach this step by step, then execute.”
- “Review my current draft/plan and improve it using OpenClaw Official Skills Collection. Call out assumptions.”
- “Produce a checklist I can reuse whenever we run OpenClaw Official Skills Collection on similar work.”
Use cases and examples
- Obsidian note workflows
- Gmail/calendar via gog bridge
- GitHub repo management
- Slack messaging automation
- CI/CD monitoring
- First-week trial of OpenClaw Official Skills Collection on a real operations workflow
Prerequisites
- Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
- Network access if the skill fetches guidelines or calls external tools
- Project or brand context (CLAUDE.md / product notes) for better outputs
- Permission to install third-party skills — audit SKILL.md and scripts first
- Clear success criteria — agents run multi-step workflows and need a defined “done”
Tips
- Keep descriptions/triggers tight so OpenClaw Official Skills Collection fires only when relevant (avoids context tax).
- Prefer one sharp job over a mega-skill that tries to do everything.
- Pair with verification (tests, review, screenshots) before shipping outputs.
- Re-audit installed skills monthly — unused skills still cost context every turn.
- Give agents scoped tools and sandbox risky actions (filesystem, deploys, payments).