Loading...
Loading...
Found 9,476 Skills
Export paper from CNKI and push to Zotero, or save as RIS file. Use when user wants to save a paper to Zotero or export citation data.
Invoke when the user asks about art style, visual language, style guide, character design, environment art, UI art direction, asset pipeline, reference boards, color palette, or shape language. Triggers on: "art style", "visual", "style guide", "character design", "environment art", "asset pipeline", "color palette", "shape language". Do NOT invoke for UI/UX layout (use game-ux-designer) or creative vision (use game-creative-director). Part of the AlterLab GameForge collection.
OpenAI Codex (CLI / IDE / cloud) の公式リファレンス。 codex CLI, codex exec, AGENTS.md, rules, subagents, prompting, approvals, sandbox, permission profiles, auto-review, config.toml, profiles, MCP 設定, 環境変数, GitHub Action, Codex SDK, Agents SDK 連携, cloud 委譲, administration, roles, provisioning, analytics API, compliance API, Codex Security 脆弱性スキャン, deep scan, triage, findings, SARIF export, threat model, security hardening, cloud / local / worktree 環境, git worktrees, Record & Replay, GitHub / Linear / Slack 連携。
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
Check that an Open Knowledge Format (OKF) bundle is conformant with the v0.2 spec (§11). Use when asked to validate, lint, or check an OKF bundle, or before committing changes to one. Runs a deterministic Python checker — not an eyeball pass. Also migrates a v0.1 bundle to v0.2 in place with `--migrate`.
Generate and install a complete favicon / app-icon / PWA-icon stack directly into a project — favicon.ico, every PNG size, apple-touch-icon, Android icons, theme-aware light/dark favicons, per-environment (dev/staging/prod) variants, and manifest.json — from an emoji, a named icon, a logo file, or an image URL. No browser, no zip download, no manual unzip: files land in the repo and the <head> gets patched. Use whenever a user wants a favicon, site icon, tab icon, app icon, or PWA icons, or says "make me a favicon", "add a favicon", "add app icons", "generate icons for this site", or "I want a <emoji>/<logo> as the favicon". A new app with no icon looks unfinished — this fixes it in one shot. Powered by favicontools.com.
Stand up (or extend) an operator-only in-app scratchpad / internal test-bed — a single gated internal page that reuses the project's real components and library functions so you can judge work-in-progress by eye: eyeball generated visuals (OG/social cards, emails, avatars, empty states), compare variants side by side or with live sliders, check config/env readiness, and exercise real side-effecting flows with fake data — without shipping any of it to users or clicking through the whole product. Boards and config panels get a "Copy as JSON" button so a tuned-by-eye result round-trips straight back into the code or to an agent to apply. Bootstraps into the user's existing stack: detects the framework, auth, and env conventions, writes a fail-closed access gate first, then a route with a section switcher seeded from their own code. Use when a user says "spin up a scratchpad", "internal test bed / dev playground / sandbox page", "an operator/admin preview page", "a page to eyeball my work", "preview my OG cards / emails / component variants", "add a test page for these components", or "an internal page to exercise a flow with fake data". NOT for public/user-facing features, NOT a replacement for tests (pass/fail machine-checkable → write a test), NOT Storybook (this lives inside the real app), and NOT a place to do load-bearing production operations.
File or link CawPlan defects from failed/blocked TestRail Results via QA Insights A4. Use when: SQA wants to turn a TestRail Failed/Blocked Result into a CawPlan Ticket, paste a tests/view URL to file a defect, review an A4 defect draft, create a BUGFIX/FEATURE ticket, or link an existing ticket back to TestRail defects. Cold start with tests/view MUST call execution failures --test-id BEFORE defects draft; never use test_id as the draft path result_id. A4 write path (create-ticket) MUST use --body-file or --body JSON — never field flags like --description or --result-id. NOT for: importing test cases (use `cawplan-testcase-import`); creating TestRail Plans/Runs (use `cawplan-testplan-layout`); release risk assessment; generating requirements or test points.
Generate developer behavioral profile and create Claude-discoverable artifacts
Use when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data Tables, tags, or Gherkin embedded in Markdown.
Discover, navigate, and call Slack Web API methods (the family.method endpoints at slack.com/api like chat.postMessage, conversations.history, users.info, views.open). Use this skill whenever the developer asks which Slack API method does something, needs a method's required OAuth scopes or token type, wants to call or test a Web API method, is handling cursor pagination (next_cursor), hitting rate limits (tier/ratelimited/Retry-After), or debugging API errors like missing_scope, invalid_auth, or channel_not_found. Also trigger when they paste a slack.com/api/ URL or a docs.slack.dev/reference/methods link, or ask how to list/fetch/post/update Slack resources via the API. This skill covers the Web API method layer: finding the right method, reading its contract (scopes, arguments, errors), and calling it over raw HTTP with curl or through a Slack SDK.
Use the Slack CLI to create, run, and manage Slack apps from the terminal. Use whenever the developer wants to log in, add a team, switch workspaces, or authenticate with Slack; whenever Slack CLI commands are needed (local development with `slack run`, managing app lifecycle, the manifest).