Total 56,417 skills
Showing 12 of 56417 skills
Structure a freeform bug report into sections. Use in `prescribe` before `investigate`, or standalone whenever a raw bug report needs structuring.
Manage App Store product page promoted purchase slots using the `asc` CLI tool. Use this skill when: (1) Listing slots: "asc promoted-purchases list --app-id ID" (2) Promoting an IAP or subscription: "asc promoted-purchases create --app-id ID (--iap-id ID | --subscription-id ID)" (3) Updating visibility / enabled state: "asc promoted-purchases update --promoted-id ID --visible|--hidden --enabled|--disabled" (4) Deleting a slot: "asc promoted-purchases delete --promoted-id ID" (5) User says "promoted purchase", "promoted IAP", "feature on App Store", "App Store product page promotion", "promoted slot"
Create test data with Zenstruck Foundry v2 factories (PersistentObjectFactory, real objects); define states, sequences, and relationships
Convert an HTML document supplied in the request body to clean Markdown, stripping scripts and styles. Called as POST /v1/doc/html-to-markdown, it takes html and returns markdown, characters, inputBytes. A research agent handed raw HTML must reduce it to readable text before it can reason over it, and passing full markup through a model wastes most of the context window. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.004, paid in USDC on Base over x402.
Pulls DOIs, arXiv ids, PMIDs, PMCIDs and ISBNs out of free text, deduplicated and normalized, with the character offset of each first occurrence. Called as POST /v1/text/extract-citations, it takes text, kinds and returns count, citations, byKind. An agent handed a references section, an email or a PDF dump has to find the identifiers before it can look any of them up, and a model asked to do it by reading invents DOIs that resolve to nothing. The catalog already answers `crossref.doi-metadata` and `pubmed.citation-search`; neither could tell you what to ask them about. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.003, paid in USDC on Base over x402.
Guidance for detection engineering in Microsoft Sentinel — building, testing, deploying, and maintaining analytics rules, hunting queries, and SOAR automation. Covers the Content Hub solution model, MITRE ATT&CK mapping, scheduled vs near-real-time (NRT) vs Fusion vs anomalies analytics, KQL detection patterns (joins, summarize, bin, materialize), entity mapping and incident enrichment, custom detections from Defender XDR vs Sentinel-only, automation rules, playbooks (Logic Apps), watchlists, threat intel matching, content as code with Azure DevOps / GitHub repositories integration, and detection lifecycle (validate → tune → version). WHEN: Sentinel analytics rule, KQL detection, MITRE mapping, Sentinel content hub, scheduled analytics, NRT rule, hunting query, Sentinel automation rule, Logic App playbook, custom detection, repositories Sentinel CI/CD, detection-as-code, watchlist, threat intel matching analytics, fusion alerts, anomalies, incident enrichment, entity mapping. DO NOT USE for Sentinel architecture/onboarding (use sentinel), Defender XDR custom detections only (overlap—use the side that owns the data), or generic KQL training.
Address pull request review comments, conflicts, and CI failures. Use when a PR needs unblocking.
Async message handling with Symfony Messenger; configure transports (RabbitMQ, Redis, Doctrine); implement handlers, middleware, and retry strategies
Fetch a public web page and return it as clean Markdown with its title. Capped at 2 MB. Called as GET /v1/doc/url-to-markdown, it takes url and returns sourceBytes, title, markdown, characters. This is the third-highest-demand category observed on-chain: an agent given a link needs the readable text, not the markup, and cannot run a browser itself. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.003, paid in USDC on Base over x402.
Guidance for threat modelling using STRIDE and the Microsoft Security Development Lifecycle (SDL). Covers data-flow diagrams, trust boundaries, the STRIDE categories, mitigation mapping, and tooling (Microsoft Threat Modeling Tool). WHEN: threat modeling, STRIDE, data flow diagram, trust boundary, identify threats, SDL threat modeling, security design review, threat model a system, mitigation mapping, Microsoft Threat Modeling Tool, secure design review, design-time security. DO NOT USE for org-wide security architecture (use security-architecture) or for runtime detection (use sentinel / defender-xdr).
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
Create and manage Doctrine migrations (lib 4.x) for schema versioning; handle dependencies, rollbacks, and production deployment