Loading...
Loading...
Found 2,827 Skills
Design CI/CD pipelines that run test suites. Covers GitHub Actions and GitLab CI templates, parallelism and sharding, artifact management, flaky-test quarantine, test-result publishing, coverage quality gates, OIDC keyless deploy, and copy-paste workflows for Playwright, Jest, and multi-stage pipelines. Use when: "CI/CD," "GitHub Actions," "pipeline," "test in CI," "GitLab CI," "continuous integration," "test automation pipeline," "shard tests in CI." Not for: per-test flaky healing at runtime — use test-reliability; go/no-go release decisions and smoke-test checklists — use release-readiness; test-result dashboards and trend reporting — use qa-metrics. Related: playwright-automation, qa-metrics, test-reliability, coverage-analysis, release-readiness.
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).
Embed screenshots, images, diagrams, GIFs, and screen recordings in GitHub PRs and issues — or stage them ahead of a PR, collect them into one attachments comment, or get a durable public link to share a visual with a person. Use this whenever a visual needs to end up in a PR description, issue body, or PR/issue comment, in front of a teammate, or saved for a PR that doesn't exist yet. Triggers include "attach a screenshot to the PR", "add a before/after to the issue", "include a screenshot of …", "share a GIF of the flow", "record the bug and put it in the issue", "get me a link I can paste in Slack", "stage screenshots for the PR", "attach this when I open the PR", "save this for the PR", "collect the PR's media", or having just captured or changed something visual that a shot would make clearer — even mid-task, before a PR exists. Also applies when an agent has no local filesystem and is uploading via the hosted MCP (agents.uploads.sh). Reach for this instead of drag-and-drop or github.com/user-attachments (agents can't upload there) and instead of hand-rolling cloud-storage uploads. Capture the visual with whatever browser or screenshot tooling you have; this skill covers hosting and embedding it.
Audit an ENTIRE codebase with multiple agents in parallel — map the repo, partition it into review slices, fan out one (or more, multi-lens) reviewer subagent per slice, reduce with a cross-cutting/architecture critic + a completeness check, then triage, fix, and report with an honest coverage ledger. Use when asked to 'audit the whole codebase', 'full security/quality review of the repo', 'review the entire project', 'do a deep/comprehensive code audit', 'scan everything for bugs or vulnerabilities', when onboarding/inheriting an unfamiliar repo, or for a periodic deep sweep. Whole-repo scoped and scales agent count to repo size — NOT a diff review (for changed lines use dual-agent-review).
Integrate insurance into a financial plan: decide what risks to retain vs transfer, size life insurance with needs-based and human-life-value analysis, and evaluate disability, long-term care, annuity, and liability coverage. Use when the user asks 'how much life insurance do I need', 'term vs whole life', about 'disability insurance' (own-occupation vs any-occupation, group vs individual), 'long-term care' insurance or self-insuring LTC, 'should I buy an annuity' (SPIA, DIA, variable, indexed), or an 'umbrella policy' for liability protection. Also trigger on 'DIME method', 'life insurance calculator', 'whole life vs invest the difference', 'elimination period', 'benefit period', 'hybrid LTC policy', '1035 exchange', 'beneficiary review', or questions about insurance riders, surrender charges, or whether an advisor can recommend insurance products.
Strip AI-script tells from a TikTok spoken script and caption so it sounds like a person talking on camera, not a teleprompter. Removes em dashes, AI vocabulary (leverage, fundamentally, delve, harness), rule-of-three lists, written-not-spoken phrasing, and "hey guys" filler, then adds contractions and one specific number. Includes a --mode audit pre-film check (hook strength, completion design, caption fit). Use before filming any AI-drafted script. Not for writing from scratch (use tt-hook-scripter).
Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's "Optimise Forge platform costs" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve scheduled triggers, reduce KVS writes, move work to the frontend, use bridge APIs, batch API calls, add caching, or evaluate Forge Remote trade-offs. By default, perform an audit first and offer to make the recommended changes after presenting the audit. Only modify files immediately when the user explicitly asks the agent to implement or apply optimizations.
Use when auditing a Datex Studio component file before merge — final gate after authoring or modifying any component (action, function, grid, hub, form, editor, selector, storage, customType, backendTest, datasource). Generic dispatcher: reads the component file, picks the matching creator skill's rule set by file suffix, and runs the audit per those rules. Output is a structured punch-list (Blockers / Warnings / Nits). Triggers: "audit a component", "check it before merge", "final gate after authoring or modifying". For grid-specific gotchas (envelope shape, text-display coercion) use grid-validator instead.
Reduce AWS spend with rightsizing, autoscaling, commitment planning, and storage lifecycle policies. Use when running FinOps reviews, lowering cloud bills, or improving cost-per-request metrics.
Manage container registries including ECR, ACR, GCR, and Docker Hub. Push and pull images, configure authentication, set up repository policies, and implement image lifecycle management. Use when working with container image storage and distribution.
Orchestrate AI/ML pipelines for data ingestion, model training, batch inference, and RAG indexing using Prefect, Airflow, or Dagster. Build reliable, observable, and retriable workflows for production AI systems.
Only applicable to regular spreadsheets Sheet and multidimensional tables Bitable/Base, not a universal entry for all data or JSON requests. Use this Skill when users need to read/write cells, import/export tables, set styles/filter views/conditions/drop-down boxes/floating images, or operate on tables, fields, records, views, roles, collaborators, dashboards, forms, workflows, and data aggregation of multidimensional tables; it must also be used for cron/unattended Bitable scenarios with --as bot. It is explicitly prohibited to use it for document permissions/collaborators, message/event subscriptions, and unencapsulated OpenAPI universal passthrough; use feishu-cli-storage, feishu-cli-messaging, and feishu-cli-platform respectively for those scenarios. Use feishu-cli-docs for Markdown tables in documents; use feishu-cli-visual for data chart display.