Catalogue de skills·2424 skills
Tous les skills
Des skills prêts à l'emploi — copie le Markdown du skill et colle-le dans ton agent.
Compatible avec
Liste des skills du catalogue Arboris
2424 skills sur 2424
Skill
Description
Agents
Copier le skill
Pattern Radar (Microsoft)Agents & Orchestration100Scan the user's recent Microsoft 365 signals (emails, active chats/channels, calendar subjects) to surface recurring patterns worth productizing — either as a blog post (the user explains the same thing repeatedly) or as an automation (the user does the same multi-step task repeatedly). Use when the user asks "what should I write about?", "what could I automate?", "find patterns in my work", or invokes "/pattern-radar".
Peft Method Changes (Hugging Face)Agents & Orchestration100Use when modifying an existing PEFT method (its forward method, parameters/buffers, state_dict handling, or config defaults) to ensure that existing checkpoints keep working.
Performance Analysis (Microsoft)Produit & Go-to-market100Summarizes fixed A/B and campaign scenarios for a Marketing Director without claiming live results.
Performance Benchmark (.NET)Infra, Ops & Workflow100
Generate and run ad hoc performance benchmarks to validate code changes. Use this when asked to benchmark, profile, or validate the performance impact of a code change in dotnet/runtime.
Performance Dashboard (Microsoft)Agents & Orchestration100Gives a Sales Manager role-cohort coaching signals without profiling workers or making employment decisions.
Perl TestingTests100Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology. Use when writing Perl tests with Test2::V0 or Test::More, or measuring coverage.
Persona Content CreatorAgents & Orchestration100
Create, organize, and distribute content across Workspace.
Persona Customer SupportProduit & Go-to-market100
Manage customer support — track tickets, respond, escalate issues.
Persona Event CoordinatorAgents & Orchestration100
Plan and manage events — scheduling, invitations, and logistics.
Persona Exec AssistantAgents & Orchestration100
Manage an executive's schedule, inbox, and communications.
Persona Hr CoordinatorAgents & Orchestration100
Handle HR workflows — onboarding, announcements, and employee comms.
Persona Project ManagerAgents & Orchestration100
Coordinate projects — track tasks, schedule meetings, and share docs.
Persona Reaction Panel (Microsoft)Frontend & UI100Pre-simulate how a defined set of role-based personas will react to an internal comms, launch, or enablement artefact before it ships. Use when the user asks to "run the persona panel", "pressure-test this comms against our personas", "QA this launch email/deck before it goes out", "how will each team react to this", or wants persona- and domain-level feedback on a broad internal artefact. Requires a personas file — bring your own (see references/personas.template.md). Do NOT use for 1:1 private comms, HR/performance matters, or legal/contractual language.
Persona ResearcherDonnées & Recherche100
Organize research — manage references, notes, and collaboration.
Persona Sales OpsAgents & Orchestration100
Manage sales workflows — track deals, schedule calls, client comms.
Persona Team LeadAgents & Orchestration100
Lead a team — run standups, coordinate tasks, and communicate.
Pg Security Release Analysis (Supabase)Auth & Sécurité100
Generate a CVE catalog + Supabase impact analysis for a PostgreSQL security release. Use when reviewing a new upstream PG quarterly security release to decide what to ship and how to communicate. Inputs are the version ranges (e.g. REL_15_14..REL_15_18 + REL_17_6..REL_17_10); output is a draft catalog markdown ready to post on the breaking-change-analysis Linear ticket.
Phase New (Ansible)Agents & Orchestration100
Create a delivery phase for grouping requirements. Use when defining roadmap phases, "add a phase", "create Phase 2", or organizing requirements into delivery milestones. Do NOT use for importing phases from a PRD (use prd-import instead) or creating requirements (use req-new instead).
Pipeline Health (Microsoft)Agents & Orchestration100Review the synthetic pipeline and show which opportunities need attention without changing the forecast.
Pirate Speak (TanStack)Agents & Orchestration100
Answer entirely as a boisterous pirate, with nautical slang and "arrr".
Plan OrchestrateAgents & Orchestration100Read a plan document, decompose it into steps, classify each step, and emit the ready-to-paste ECC slash command for that step, carrying the step identifier and scope in the command's own documented argument form. Generative only — never invokes commands itself and never claims to control what a command runs internally. Steps whose command cannot carry plan scope fail closed instead of being emitted. Use when the user has a multi-step plan and wants the right command for each step without picking it by hand.
Plan UI Change (.NET)Docs & Écriture100
Plan complex Blazor UI features by decomposing them into focused components. USE FOR: building a complex Blazor page with multiple sections, planning component decomposition, designing a multi-section dashboard or layout, breaking down a large UI feature into composable components, pages with sidebars and content panels, any page with 3+ distinct visual sections or multiple interacting sub-features, identifying parent-child relationships and data flow. DO NOT USE FOR: creating new Blazor projects or apps from scratch (use create-blazor-project), implementing a single individual component (use author-component), writing component code with parameters and EventCallback (use author-component), or simple single-component pages.
Plankton Code QualityVérification100
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks. Use when setting up write-time formatting, linting, or auto-fix hooks on file edits.
Platform Detection (.NET)Tests100
Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for "which test platform/framework?", "VSTest or MTP?", or "what runner does this project use?", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest/MTP configuration. Resolves global.json, project, packages.config, Directory.Build.props, and Directory.Packages.props precedence for MSTest/xUnit/NUnit/TUnit. DO NOT USE when the user asks to run/filter tests or for commands, flags, TRX/dumps, or test-command/filter errors; use run-tests directly. Do not route hot-reload or migration requests here as the entry skill; mtp-hot-reload may use this skill internally for platform detection.
Plugin Discovery Patterns (Microsoft)Langages & Runtimes100Use when making a system extensible with runtime plugin discovery via Python entry points, a file-based plugin registry, multi-backend provider abstractions, or schema-driven input validation.
Pm The Docs (Supabase)Produit & Go-to-market100
Docs-PM decision support for the "Write the docs" authoring process — makes audience, stage, and cross-cutting scope calls during the Frame and Shape stages (including cross-repo product lookup via universe when accessible, else the public OSS path), and helps decide when a docs question needs to self-serve vs. escalate to a docs PM. Use when framing a new docs page or launch, deciding what product stage or audience a feature targets, judging whether a docs question needs PM sign-off, or confirming which product repos a launch spans.
Points Summary (Microsoft)Produit & Go-to-market100Helps a CRM Manager explain a synthetic points balance without changing a ledger.
Post Scenario Completion (Microsoft)Agents & Orchestration100Generic guidance for presenting scenario completion and next-step recommendations to the user
Postgres PatternsBackend & API100PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices. Use when designing PostgreSQL schemas, indexes, or RLS policies, or when a query is too slow.
Postmortem (.NET)Infra, Ops & Workflow100
Write a postmortem for a regression that escaped to production, broke real users, and traces back to a design flaw worth documenting for future implementors. Only invoke after confirming no existing postmortem or doc covers the same root cause.
Pov Line Generator (Microsoft)Agents & Orchestration100Use this skill when the user asks for a point of view, punchy line, positioning sentence, provocative statement, headline angle, opinion line, or concise strategic stance.
Power Automate Documentation (Microsoft)Docs & Écriture100Trigger whenever the user uploads or references a Power Automate solution `.zip` and asks about references, dependencies on other flows, or related questions — phrasing like "document this flow", "what does this flow read/write/touch", "map the connection references", "audit this solution", or "which flows call which".
Power Bi Model Review (Microsoft)Docs & Écriture100Use this skill whenever the user shares a Power BI or Analysis Services semantic model (a TMDL export, a BIM/JSON model definition, or a pasted list of tables, relationships, and measures) and asks for a model review, a performance check, or help fixing DAX, before writing or correcting any DAX measure for that model.
PR (Storybook)Agents & Orchestration100
Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.
PR Build Status (.NET)Infra, Ops & Workflow100
Retrieve and analyze Azure DevOps build failures for GitHub PRs. Use when CI fails. CRITICAL: Collect ALL errors from ALL platforms FIRST, write hypotheses to file, then fix systematically.
PR Description (.NET)Infra, Ops & Workflow100
Use when drafting, proposing, creating, or editing prose for a dotnet/fsharp GitHub PR or issue — body, title, comment, review summary, edits — including bare asks like "open a PR", "ship this", "write up what I did", "summarise the change", "reply on the PR", "edit the issue body", "gh pr create", "gh pr comment", "gh pr edit --body", "gh issue comment", "gh pr review --body". Primary use case is PR descriptions; same rules apply to PR/issue comments and review summaries. Not for labels, reviewers, merging, or code-review findings (just the prose write-up of them).