Loading...
Loading...
Found 2,094 Skills
This skill should be used when the user asks to "self-publish", "publish my book", "ISBN", "copyright page", "book metadata", "BISAC", "keywords", "KDP", "IngramSpark", "Draft2Digital", "go wide", "Kindle Unlimited", "print interior", "trim size", "paperback", "ebook", "EPUB", "cover wrap", "spine width", "pricing", "launch plan", "ARC team", "advance readers", "newsletter", "reader magnet", "Amazon ads", "BookBub", "rights", "foreign rights", "audio rights", "film rights", "publishing contract", or wants to take a finished manuscript through production, distribution, launch, and rights management. It owns contracts and rights sales; NOT for permission to quote lyrics, epigraphs, or other material in the book (use editorial-review), or for drafting the blurb or retailer description (use submission).
Expert NIST Cybersecurity Framework (CSF) advisor covering CSF 2.0 and CSF 1.1. Use this skill whenever a user asks about NIST CSF, cybersecurity risk management, the six CSF functions (Govern, Identify, Protect, Detect, Respond, Recover), CSF profiles, implementation tiers, gap assessments, organizational profiles, community profiles, CSF core subcategories, informative references, or mapping to other frameworks (NIST SP 800-53, ISO 27001, CIS Controls, COBIT). Also trigger for questions like "how do I implement NIST CSF?", "what does CSF 2.0 change?", "help me build a CSF profile", "how do I assess my cybersecurity posture?", or any request involving organizational cybersecurity risk strategy or framework alignment.
Build a product launch video in Remotion from a brief: a launch film, feature announcement, version release, Product Hunt / X / LinkedIn promo or landing-page hero video. Composes snapcn's hand-tuned Remotion scenes (@snapcn/announce-title, hero-launch, type-morph, count-grid, wordmark-cut and more) instead of hand-animating every shot, so the result does not look like every other AI video. Brief → storyboard → install snapcn components → compose → render-audit → ship. Triggers: launch video, product launch video, remotion launch video, announcement video, release video, promo video, Product Hunt video, "make a video for my launch", "make a launch film with Claude Code".
Use when the user wants to download OpenHarmony daily build images or flash them to a real device (DAYU200/RK3568 or others). Triggers on daily build, DAYU200, RK3568, flashing, burning, hdc reboot, upgrading firmware.
Answer business questions about the org's RevOS data directly in chat by querying its live semantic model over MCP — "how many orders…", "revenue by…", "top N…", "trend over time…", "compare X to Y…" — and schema-discovery questions like "what's in my semantic model", "what can I query", "list cubes/datasets/fields", "describe a cube" — or when explicitly asked to "query the semantic model", "run a cube query", "show me a chart", "plot…", "graph…". Use this whenever you would otherwise call the RevOS api_read tool against the `cubes` resource directly — this skill is what turns its raw JSON into a rendered table, a chart when the shape fits, a safe choice of join path when a query spans multiple cubes, and a plain-English explanation, instead of a dumped tool result. This applies even when the question names a specific source system (HubSpot, Zammad, Exact Online, …) — answer aggregate/analytical questions from the semantic model, not a direct source connector.
Convene a council of AI coding agents before finalizing a plan. The agent you're talking to — whichever CLI is the lead (claude, codex, cursor, gemini, grok, opencode) — drafts a plan, presents it independently to every other agent CLI installed on the machine, each member gives ONE reply per turn, and the lead revises the plan for X turns before answering. Trigger words: council, convene the council, consult the other agents, ask the council, ask codex/cursor/gemini/grok what they think, second opinion from other agents, N turns of deliberation, deliberate before planning.
Create, change and debug openQA tests and review openQA results. Use whenever the user mentions openQA, o3, os-autoinst, isotovideo, testapi calls such as assert_script_run or assert_screen, needles, a job URL such as openqa.opensuse.org/tests/123, an openQA job group or build, soft-failures, force_result or verification runs, or asks why an openQA job failed, how to write, schedule, run or fix an openQA test or review a test PR, or to review or label openQA results. Tests: os-autoinst test modules in Perl or Python, YAML schedules, test data, pull requests to os-autoinst-distri-opensuse or a custom test distribution. Results: triage a failed, incomplete or timed-out job from its logs, sweep a job group or build, classify product bug vs test issue vs infrastructure, draft bug reports and job comments whose bugrefs, labels and carry-over openQA parses. Not for OBS package build failures, maintenance-update validation with mtui, plain bug-tracker work, other CI systems or general Perl questions.
Use when preparing or performing a review delegated to a subagent, or coordinating its findings, authorized fixes, and re-review. Applies to reviewer subagents invoked through the host application’s delegation features or through CLI tools, including review phases within another task. Don’t use merely for a main agent’s direct review or self-review, reports supplied from another conversation, or standalone findings verification.
Settle every decision behind a plan before anything gets built, in rounds. Opens with a kill condition that can end in a cut, closes with a decision record. Use when a plan, feature, or design needs pressure-testing before a spec exists, when the user says "interview me", "grill me", "pressure-test this", "poke holes in this", or "before we plan this", and when another skill needs the decisions settled before it writes anything. Draws the design tree as a page when it grows or when asked to "show me the tree".
Detect the env manager and bootstrap the runtime, agent-tools, and composed development environments. Detect with `python -m skore_skills env detect`, persist the manager and `env.managed`, then `env init --manager`, `env sync --execute`, install Skore for a recorded hub or mlflow destination (plain Skore when unset or local), and `env verify --execute`. Does not add other stage ML libraries. TRIGGER when the user asks for the env manager, pixi, uv, or a Python environment, or when none is recorded yet. SKIP later packages (add-python-package). SKIP scaffolding src/ (setup-workspace). HOW TO USE: detect, ask managed vs user-managed, ask the manager when needed, then env init, env sync, add Skore, and env verify. When setup-ml-project dispatched this turn, skip each ask whose answer is already recorded. One recorded answer does not skip the other ask.
Read and analyze message queues, system history log, reply lists, and message file definitions on IBM i via SQL services. Use when user asks about: (1) reading QSYSOPR or other message queues, (2) searching the system history log (QHST), (3) finding high-severity messages, (4) viewing the system reply list, (5) looking up message definitions (CPF, MCH, SQL messages), (6) message severity analysis, (7) replacing DSPMSG, DSPLOG, WRKMSGQ commands, or (8) any message handling or troubleshooting task.
Fix a Sanity Studio custom form component (components.input, components.field, components.item, or a plugin's form.components) that suspends without its own Suspense boundary, so it loads without layout shift and never blocks new documents. Use when the console warns "The custom input/field/item component ... suspended without a <Suspense> boundary of its own" or "A form component ... suspended without a <Suspense> boundary of its own", when a custom form component uses React.lazy, use(), App SDK hooks (useDocumentProjection, useQuery, useDocument) or another suspending data library, or when a field or array item shows a skeleton that never goes away on new documents.