Loading...
Loading...
Found 138 Skills
This skill provides instructions for interacting with Todoist using the td CLI tool. It covers CRUD operations for tasks/projects/sections/labels/comments, and requires confirmation before destructive actions. Use this skill when the user wants to read, create, update, or delete Todoist data.
Execute specifications from workspace platforms into implementation. Transforms documented specifications into actionable development tasks.
Create, deploy, and interact with agents on TerminalUse. Use when user mentions "tu", "terminaluse", "deploy agent", "create agent", "agent task", "filesystem", or wants to build/test/run an agent.
Interact with Dida365 Open API using Python CLI to manage TickTick tasks/projects, suitable for scenarios where you need to call TickTick APIs via scripts or command line (such as querying, creating, updating, completing, and deleting projects/tasks).
Create dex task from markdown planning documents (plans, specs, design docs, roadmaps)
Plan and stay on track. Fast. Practical. Intentional. Oya is a productivity tool for doers who think strategically. It combines your long-term vision with daily adaptation by bringing together ideas from Getting Things Done (GTD) and the 7 Habits of Highly Effective People in a simple and lightning fast workflow. Daily use is recommended. Just say "oya" to get going.
Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
Documentation-as-Source-of-Truth workflow. Use when working with projects that use docs/ as the canonical source for definitions, rules, and tasks. Routes to specialized sub-skills for specific documentation types.
Check Meilisearch index status, tasks, health, and settings. Use for debugging search issues, monitoring indexing tasks, and inspecting index configuration. Read-only admin operations.
Standardized artifact creation via tk tickets. Use whenever a skill needs to persist output — research findings, plans, postmortems, reviews, design specs, decisions. Replaces all bespoke output directories (.oracle/, .plans/, etc.) with a single canonical system.
Apply OpenSpec OPSX in a strict one-task-at-a-time loop. Use when the user asks to execute work as single-task changes, wants spec-first implementation per task, or says to use OpenSpec method for each task from a task list. Supports both native /opsx command environments and manual fallback by creating OpenSpec artifact files directly.
Use when writing async/await code, enabling strict concurrency, fixing Sendable errors, migrating from completion handlers, managing shared state with actors, or using Task/TaskGroup for concurrency.