Shared

Shared (company-wide)
Space owner	@apd-evalentine, @apd-bbrewington, @apd-mozgen (DS-prefixed: @apd-evalentine)
Skills	5 launched 1 in review · 6 proposed
Folder	`skills/shared/`
Backlog	Skill Idea issues

Home › Shared

Skills every APDer can use regardless of practice: brand, design, decks, and general code/documentation utilities. If a skill would help more than one subpractice, it belongs here.

For rules on sharing client material, see Handling Outputs.

Skill catalog

Brand & content

Skill	Version	What it does	Invoke
`apd-brand-voice`	2.4	Writes Aimpoint copy in the brand voice: web pages, case studies, blogs, social, proposals, emails. Pattern-matches against real website copy in its references. Deck slide text is handled by `apd-pptx-design` instead.	`$apd-brand-voice` / `/apd-brand-voice`
`apd-design-brand`	2.4	The canonical Aimpoint visual design system (colors, typography, principles) for non-PPTX deliverables: HTML, React, PDF, mockups, dashboards. If skills conflict on design, this one wins.	`$apd-design-brand` / `/apd-design-brand`

Presentations

Skill	Version	What it does	Invoke
`apd-pptx-design`	2.8	Builds Aimpoint decks end-to-end: storyboard → layouts → diagrams → pptxgenjs build → template merge → visual QA. Self-contained; don't also load the brand skills for a deck run. Requires Node.js 22+; dependencies are vendored (no npm/pip/network).	`$apd-pptx-design` / `/apd-pptx-design`

Data science utilities

Skill	Version	What it does	Invoke
`apd-ds-code-review`	1.0	Prioritized review report for Python/SQL in ML pipeline and data platform contexts. Trigger with "code review".	`$apd-ds-code-review` / `/apd-ds-code-review`
`apd-ds-document-project`	1.0	Generates function docstrings across a project plus a high-level overview markdown.	`$apd-ds-document-project` / `/apd-ds-document-project`

Which skill when?

Building a NEW deck ............... apd-pptx-design (alone)
Proposal → SOW draft .............. apd-proposal-to-sow (lives in Pre-Sales)
Writing copy (not slides) ......... apd-brand-voice
Styling anything non-PPTX ......... apd-design-brand
Reviewing ML/data code ............ apd-ds-code-review
Documenting a codebase ............ apd-ds-document-project

Where skills fit the shared stack

How launched skills, work in review, and the idea backlog map onto the stack: Brand & content · Presentations · Developer utilities · Enablement · Infrastructure · External skills.

Launched

Skill	Stage	What it does
`apd-brand-voice`	Brand & content	Aimpoint copy in the brand voice across every non-deck format
`apd-design-brand`	Brand & content	Canonical visual design system for non-PPTX deliverables
`apd-pptx-design`	Presentations	End-to-end branded deck builds with template merge and visual QA
`apd-ds-code-review`	Developer utilities	Prioritized Python/SQL review for ML and data platform code
`apd-ds-document-project`	Developer utilities	Project-wide docstrings plus overview markdown

In review

PR	Skill	Stage	Status
#12	Create feature branch skill	Developer utilities	Open PR by @apd-psefton, changes requested

Proposed

Issue	Skill idea	Stage	What it does
#75	Template pptx content build out	Presentations	Fills the standard template, vs. bespoke slides from `apd-pptx-design`
#59	App discovery & development for non-technical users	Enablement	Guides non-technical APDers from idea to working application (@apd-vkhanna)
#21	Multi-LLM Skill Packaging and Upstream Sync	Infrastructure	One packaging pipeline across Claude, Codex, and Cortex
#56	Shared organization-level skills (research)	Infrastructure	How to distribute skills org-wide (@apd-ypuranik)
#42	Microsoft/Azure skills in `external_skills.yml`	External skills	Widens the vetted external index
#43	AWS skills in `external_skills.yml`	External skills	Widens the vetted external index

The launched stack came out of the early pptx and eval-harness issues (#2, #5, #48, all closed); current backlog energy is on infrastructure and the external-skills index rather than net-new content skills, leaving Enablement thin at a single idea (#59).

Playbook tips

The pptx/brand trigger boundaries are deliberate: decks are self-contained in apd-pptx-design, everything else styles via apd-design-brand
Provide real context and real facts; declarative brand voice with no substance produces empty confidence
DS utilities run best in Claude Code / Codex against an open repo, not on pasted snippets

Skill ideas / roadmap

Candidates for the shared stack. Open a Skill Idea issue to claim one, or pick up an existing tracked idea:

Tracked as issues (6 open, mapped on the areas above)

- [ ] [#75](https://github.com/Aimpoint-Digital/apd-agent-skills/issues/75) Template pptx content build out - [ ] [#59](https://github.com/Aimpoint-Digital/apd-agent-skills/issues/59) App discovery & development for non-technical users - [ ] [#21](https://github.com/Aimpoint-Digital/apd-agent-skills/issues/21) Multi-LLM Skill Packaging and Upstream Sync - [ ] [#56](https://github.com/Aimpoint-Digital/apd-agent-skills/issues/56) Shared organization-level skills (research) - [ ] [#42](https://github.com/Aimpoint-Digital/apd-agent-skills/issues/42) Microsoft/Azure skills in `external_skills.yml` - [ ] [#43](https://github.com/Aimpoint-Digital/apd-agent-skills/issues/43) AWS skills in `external_skills.yml`

Unclaimed candidates (not yet tracked, open an issue to claim)

- [ ] _None yet; shared has the highest quality bar (see below), so propose via a Skill Idea issue before building_

Contributing here

Shared is the highest-traffic folder, so the quality bar is highest: skills must be broadly useful, proven across multiple users, and conflict-free with the existing set (e.g. clear trigger boundaries like the pptx/brand split above). Propose via a Skill Idea issue before building.

Contacts

Space owners: @apd-evalentine, @apd-bbrewington, @apd-mozgen (DS-prefixed skills: @apd-evalentine)
Questions → Office Hours or the Support Desk