Skills
99,064 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Control Android cloud phones via the `pb` CLI. Make sure to use this skill whenever the user mentions logging into apps, installing apps, browsing on a phone, opening an app (Twitter, Google Play, WeChat, Instagram, TikTok, WhatsApp, Telegram, etc.), searching on phone, checking what's on screen, taking screenshots, tapping buttons, typing text, swiping, or any task that involves an Android device. This skill applies even if the user doesn't say "phone" or "pb" — phrases like "help me log in to Twitter", "install WeChat", "open Google Play", "search for something", or "check the screen" all imply phone operation. Always prefer pb over desktop browsers or Playwright for mobile and app tasks.
When the user wants to optimize picker routes, minimize travel distance in warehouses, or improve picking efficiency. Also use when the user mentions "pick path optimization," "warehouse routing," "travel distance minimization," "TSP in warehouses," "S-shape routing," or "optimal pick sequence." For order batching, see order-batching-optimization. For warehouse slotting, see warehouse-slotting-optimization.
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
Orientation and navigation for what Portaly's open APIs can do — subscription payments, digital products, discount codes, buyer promotion, subscriber self-service, order/invoice queries, and email — plus an API catalog and where to find Portaly's API docs. Trigger when the user asks "what can Portaly do", "what APIs does Portaly have", wants a list or catalog of Portaly's APIs/endpoints, is evaluating Portaly's payment or product APIs before committing to an integration, is looking for Portaly API documentation, or is deciding which Portaly skill to install.
Software development engine for coding. A production-grade skills system for web apps and mobile architecture, APIs, databases, web, mobile, AI, security, UX, SaaS, and ERP engineering. Encodes reusable engineering judgment through layered baseline and specialist skills to help generate secure, scalable, maintainable, high-performance software systems
Identify and leverage potential-energy gaps (efficiency / scale / cognition / gravity) to choose a high-potential position that amplifies the competitiveness of an individual or organization. Applies to career choices, startup direction decisions, and industry trend analysis. Use this skill when you face a decision about "which platform/company/industry to choose," or want to understand why equal effort yields vastly different results. Not applicable to the execution stage where the track is already locked in and only hard work remains (at that point, return to improving specific abilities), nor to purely internal management optimization (potential energy is an external lever). Key trigger signals: "why doesn't it work even though I try so hard," "industry A or industry B," "does this industry still have a future," "how do I ride the momentum."
Dual-axis (Standards∥Spec) multi-perspective PR review with confidence ≥80 filtering, severity calibration, plan alignment, and optional GitHub/GitLab review comment. Best-of: Claude /code-review pipeline + mattpocock dual-axis + Superpowers plan/severity habits. Triggers — 「PR 代码审查」「审查这个 PR」「code-review」「/code-review」「审 PR」「pull request review」「双轴审查 PR」 / pr code review, review this PR. Do NOT use as a name alias for mattpocock code-review or Superpowers requesting-code-review.
Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete, professional PRD. Use when starting a new feature, product, or project. Triggers on 'write PRD', 'create PRD', 'new feature', 'product requirements', or '/prd'.
Prepare Sprint 0 (walking skeleton) for a project based on its Tech Design and ADRs: classify ADRs as cross-cutting or story-specific, define the route ownership map by role, write the skeleton's Definition of Done, propose a plan, and stop for human approval. Use when the LEAD (or user) needs to prepare, plan, or initialize a project's Sprint 0 / walking skeleton before any user story is built.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.
Use when the user needs to write or run unit, functional, or integration tests for TLPP code using ProBat (tlppCore's native testing engine) -- covering @TestFixture, @Test, @Setup/@TearDown, @OneTimeSetUp/@OneTimeTearDown, @Skip, @ErrorLog annotations, the full assertion library (assertEquals, assertTrue, assertVector, assertJson, assertIsRegExFull, etc.), SKIPASSERT, and TDD/CI workflows. Also triggers on Portuguese phrasing like "testes unitarios", "criar teste ProBat", "testar rotina TLPP", "cobertura de testes", or requests to add @Test methods to a TLPP class.
Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases.
Product changelog and release notes that users actually read. Covers categorization, user-facing language, visuals, and distribution. Use for: release notes, changelogs, product updates, feature announcements, versioning. Triggers: changelog, release notes, product update, version notes, what's new, feature announcement, product changelog, update log, release announcement, version release, product release, ship notes
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Senior product manager for end-to-end product development from requirements to design. Use when users need: (1) Requirements analysis and product direction, (2) User personas and scenario analysis, (3) Feature and interaction design, (4) PRD writing, (5) Feasibility assessment. Triggers: product design, requirements, user persona, PRD, feature planning, MVP, user story.
Handling uncertainty, evaluating feedback, and independently reviewing investigation, plan, or design deliverables — the conduct baseline for questions and changes, including read-only work. Triggers on requested drafts or option sets, review findings, proposed corrections, uncertain facts or intent, consequential interpretations of behavior or ownership, "are you sure", "don't guess", "what's the latest", exact version or API claims, and reporting results. Not a change-loop skill; it governs judgment within work already underway. Covers three-source triage, discriminating checks, the clarifying interview, accuracy, bounded deliverable review, feedback judgment, and reporting in the human's language
Prepare organized packages of project files for sharing at different levels - from summary PDFs to fully reproducible archives. Creates copies with cleaned notebooks, documentation, and appropriate file selection. After creating sharing package, all work continues in the main project directory.
Продающие страницы и представительские тексты на русском языке: лендинги, промостраницы, страницы продукта, услуги, тексты о себе, профили, отклики, страницы компании, миссии и пресс-релизы. Use this skill whenever the user asks to write, audit, structure, or improve a Russian landing page, promo page, sales page, product page, service page, about-me text, job application, company page, mission, press release, homepage copy, or text describing services. Триггеры: «лендинг», «промостраница», «продающий текст», «страница продукта», «текст о себе», «отклик на вакансию», «о компании», «миссия», «пресс-релиз», «опиши мои услуги», «текст для главной». Для коротких постов см. skill post; для статей и лонгридов — statya; для текстов интерфейса — ux-copy.
Use this skill when the user explicitly asks to create, write, improve, or optimize a prompt for use with an AI. Trigger on phrases like "write me a prompt", "improve this prompt", "create a system prompt", "how do I ask ChatGPT/Claude to...", or "quero um prompt para...". Do NOT trigger for direct task requests where the user wants the output, not the prompt.
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
Use when designing or reviewing concurrent Python code — selecting between asyncio, threads, or multiprocessing; structuring cancellation and deadline propagation; bounding fan-out and backpressure. Also use when diagnosing race conditions, deadlocks, slow throughput, or thread/task leaks under load.
Python SDK for inference.sh - run AI apps, build agents, and integrate with all models. Package: inferencesh (pip install inferencesh). Supports sync/async, streaming, file uploads. Build agents with template or ad-hoc patterns, tool builder API, skills, and human approval. Use for: Python integration, AI apps, agent development, RAG pipelines, automation. Triggers: python sdk, inferencesh, pip install, python api, python client, async inference, python agent, tool builder python, programmatic ai, python integration, sdk python
Python security patterns for Django, FastAPI, and Flask. Covers Bandit, Safety, secure coding practices, and OWASP for Python ecosystem. USE WHEN: user works with "Python", "Django", "FastAPI", "Flask", asks about "Python vulnerabilities", "pip security", "Bandit", "Python injection", "Python authentication" DO NOT USE FOR: general OWASP concepts - use `owasp` or `owasp-top-10` instead, Node.js/Java security - use language-specific skills
The independent review step, second to last in the QA process. After qa-test-runner finishes execution, review the code itself from an independent perspective — checking architecture, security, concurrency correctness, data consistency, regression risk, and test coverage gaps — uninfluenced by the executor's conclusions. Produce code-review.json (with severity-graded findings and readiness constraints) which, together with the assert-code-review gate, forms the code review evidence passed to qa-report-generator for the final report. P0/P1 security issues, funding logic defects, permission vulnerabilities, and data inconsistency risks are marked as blocking. Not applicable to: generating test cases, executing tests, modifying product code (unless the user explicitly asks), report generation.
Upstream phase of QA — build a factual profile and environment evidence for the repository. Triggered when you need to collect code context for a module, index existing cases and tests, check frontend/backend service reachability, or prepare an environment snapshot. Collect facts only; do not perform risk analysis, write test cases, or judge quality. Usually executed as the first phase under the scheduling of quality-assurance-agent. Not applicable to: risk analysis, test case design, test execution, quality determination (handled by downstream phases).
The closing phase of the QA process — aggregate the artifacts of the three gates (completion, code-review, readiness), render the final HTML report, and give the final readiness determination. Triggered after qa-test-runner finishes execution and qa-code-reviewer finishes review. Read only the existing gate artifacts; do not re-run tests or review code. Not applicable to: executing tests, fixing failures, code review, test case design.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.