Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add microsoft/apm --skill apm-strategy --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Apm Strategy?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/microsoft-apm-strategy-apm)More formats (shields.io, HTML) on the badges page.
---
name: apm-strategy
description: >-
Activate for changes to project positioning, release communication,
community-facing artifacts, or breaking-change decisions in
microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release
workflows, and issue templates.
---
# APM Strategy Skill
[APM CEO persona](../../agents/apm-ceo.agent.md)
## When to activate
- Edits to `README.md`, `MANIFESTO.md`, `PRD.md`, `APPROACH.md`
- Edits to `CHANGELOG.md` (especially Unreleased and version sections)
- Changes to `.github/ISSUE_TEMPLATE/` or `pull_request_template.md`
- Release-pipeline workflow changes
(`.github/workflows/build-release.yml`, version bumps, tagging)
- Any breaking-change discussion (deprecations, command renames,
config schema breaks)
- Any decision flagged as "strategic" by another reviewer
## Key rules
- Ground every claim in `gh` CLI evidence (stars, issues, PRs,
releases, traffic, contributors). No vibes-based assertions.
- Every breaking change ships with a `CHANGELOG.md` entry and a
one-line migration note.
- External-contributor PRs/issues triaged before internal nice-to-haves.
- Position against incumbents; never name-drop them in shipped copy.
- Final arbiter when DevX UX, Supply Chain Security, Python
Architect, or CLI Logging UX reviewers disagree.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
