Oss GrowthSAFE
Agent Package Manager
Overview
Agent Package Manager
2ea90c57fbfcOBSERVED · 2026-10-08What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: oss-growth description: >- Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md. --- # OSS Growth Skill [OSS growth hacker persona](../../../.apm/agents/oss-growth-hacker.agent.md) ## When to activate - README hero / quickstart / examples sections - `docs/` content that affects first-run conversion - `templates/` (starter projects shape the second-use experience) - Release notes / launch posts / social copy - Edits to `WIP/growth-strategy.md` - Issue templates that affect the contributor funnel - Any reviewed change that the CEO flags as having growth implications ## Key rules - `WIP/growth-strategy.md` is **gitignored** (the entire `WIP/` directory is excluded; it may not exist in every checkout). Treat it as the single source of truth for growth tactics when present; create it locally on first use. Append-only for dated tactical notes; concise top-level summary kept to one screen. Never stage or commit anything under `WIP/`. - Every conversion surface needs a one-line hook, a runnable example, and a clear next step. - Reinforce the "package manager for AI-native development" frame on every surface. Cut anything that dilutes it. - Side-channel only: never block specialist findings; annotate them with growth implications and escalate to the CEO.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
2ea90c57fbfcfull audit observations/trust-audit/skill/microsoft__oss-growth.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 2ea90c57fbfc | SAFE | B | 89 | first audit |
Questions
What does the Oss Growth skill do?
Agent Package Manager
Is Oss Growth safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Oss Growth access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (2ea90c57fbfc), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.