Loading...
Loading...
Found 171 Skills
QQBot Scheduled Reminder. Supports creation, query, and cancellation of one-time and recurring reminders. Used when communicating via QQ channel and involving reminders/scheduled tasks.
This skill must be used when initializing, maintaining, and executing by-harness workflows. It applies to scenarios where users mention by-harness, harness, initialization, continuous task decomposition, executing feat, plan/build/qa/fix, session_close, automatic resumption, runtime upgrade, or need to issue Java Gate, Distributed Java Gate, and three-tier frontend specifications to constrain model coding. This skill generates independent closed-loop scaffolding, sharded task storage, session closure tools, runtime upgrade tools, and issues Java hard rule gates, distributed Java coding contracts, three-tier frontend specifications, and BYAI HTML visual references; feature_list is only used as a legacy compatibility mirror.
Manage customer service with Gladly's people-centered support platform.
Check Meilisearch index status, tasks, health, and settings. Use for debugging search issues, monitoring indexing tasks, and inspecting index configuration. Read-only admin operations.
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.
Switch into structured planning mode before outlining multi-step solutions, and exit when done.
Leave or unassign from a task you accepted on OpenAnt. Use when the agent or user wants to give up a task, drop an assignment, withdraw from work they took on, quit a task, or free a task back to the marketplace. Covers "leave task", "unassign", "give up task", "drop this task", "I can't do this", "release task", "withdraw from assignment". Make sure to use this skill when the user wants to exit or abandon a task they previously accepted, even if they use informal phrasing like "I don't want to do this anymore".
Google Sheets automation workflows - data sync, task management, reporting dashboards, and multi-platform integrations
Manage Things reminders and todo create/update requests with a deterministic MCP workflow that prevents duplicate tasks and date mistakes. Use when users ask to add, reschedule, or correct Things reminders, especially with relative dates or potential update-vs-create ambiguity.
Unified task execution protocol for Codex-only work. Supports Single Task, Epic Task, and Batch Task while preserving CSV truth-source, validation gates, context recovery, and Debug-First failure exposure. WHEN TO USE: user asks to "track tasks", "create todo list", "make a plan", "track progress", "long task", "big project", "build from scratch", "autonomous session", "跟踪任务", "自主执行", "长时任务", "从零开始", "任务管理", "做个计划", "大工程", or when a task clearly requires 3+ ordered steps that produce file changes. DO NOT USE: single-step fixes, pure Q&A, code review, explaining code, search/research tasks, tasks with fewer than 3 steps, or tasks that do not produce file changes.
Google Tasks integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Tasks data.
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.