Loading...
Loading...
Found 977 Skills
ASD-STE100 Simplified Technical English, and the reply shape a reader with ADHD can act on. A standing style rule, not an on-request tool. Layer 1 governs the words of every text a human reads — chat replies, docs, READMEs, commit messages, PR text, code comments, error messages, release notes, tool descriptions, task trackers, wiki pages. Layer 2 governs the order of a reply to a person — the next action first, numbered steps, real time estimates, no preamble and no closer. Neither layer touches code, identifiers, or command syntax. Load it before you write prose, and also when asked to remove "AI slop", make writing clear or plain, enforce a controlled style, or review text for STE violations. Two word modes — strict (procedures, runbooks, safety text, error messages) and STE-flavored (general prose, the default).
Portable QA automation agent for creating or updating automation scripts from qa-planner contracts, qa-executor signals, approved test cases, manual requests, Notion pages/databases/data sources, Plane.so work items/cards/sub-work-items, or Notion/Plane MCP payloads. Use when asked to generate or update Playwright/Cypress/other repo-native automation, update flaky or selector-broken scripts, validate automation patches, update Notion Automation Status, comment/update Plane descriptions or states, prepare automation_change_set.json, perform managed Notion/Plane sync, bridge Notion and Plane refs, produce script review or promotion review packages, or hand automation status updates back to QA agents.
Chinese technical documentation writing standards. Use when writing or revising Chinese technical documents and development docs (README, design docs, API descriptions, tutorials).
When the user wants to optimize meta tags, title, description, or hreflang. Also use when the user mentions "meta tags," "title tag," "meta description," or "hreflang."
Commit changes to git with a descriptive conventional commit message. Use when ready to commit staged or unstaged changes.
Generate graphic files in XML format (drawio) based on natural language descriptions. Supports common graphics such as flowcharts, cards, charts, icons, etc., and outputs .drawio files that can be directly opened and edited in drawio. It has exactly the same functionality as svg-generator, but outputs in drawio XML format. Triggered when users mention XML drawing, drawio, graphic generation, or flowcharts.
Full task lifecycle: create → assign → monitor → review → reject/complete. Use when asked to "add a feature", "fix a bug", "create a task", "加个功能", "修个 bug", or "/ak-task <description>".
Build fact-grounded short-form video personas and visual consistency packs from validated benchmark research. Use this when you need to define a repeatable creator archetype, image prompt pack, or persona lock for batch video production. This skill must derive personas from real benchmark evidence such as creator types, protagonist descriptions, visual styles, hooks, and audience language. Do not invent personas or visual traits without source support.
Application-developer GitOps work for OpenChoreo — onboarding Components (BYO image or source-build), authoring Workloads and `workload.yaml` descriptors, attaching PE-authored Traits, wiring component dependencies, generating ComponentReleases and ReleaseBindings via `occ` file-mode, promoting releases across Environments (single, project-wide, bulk), applying per-environment overrides, opening PRs upstream, and verifying Flux reconciliation. Use when the user says 'add a component to the GitOps repo', 'release my service via Git', 'open a PR for this Workload change', 'promote to staging via Git', 'bulk-promote my project', 'roll back a release', or operates a developer-side change from inside a scaffolded GitOps repo.
Build complete Salesforce Lightning Experience applications from natural language descriptions. Use this skill when a user requests a "complete app", "Lightning app", "business solution", "management system", or describes a scenario requiring multiple interconnected Salesforce components (objects, fields, pages, tabs, security). Orchestrates all required metadata types in proper dependency order to produce a deployable application.
Inspect a repository and propose or apply GitHub About metadata updates. Use when Codex needs to infer a concise repository description and topic set from source code, package metadata, docs config, or the current README, then preview and optionally run `gh repo edit`.
Find ALL the arXiv papers that answer a research question, using fastCRW's Firecrawl-compatible Research API. Use when the ask is to survey a literature, enumerate papers on a topic, find what a paper compares against or builds on, list the best models on a benchmark, or recover a paper from a vague description — "papers that do X", "what does X benchmark against", "best open model on Y", "find the paper that ...". Reaches 61.0% recall on the ArXivQA benchmark vs Firecrawl's Research Index 53.3%.