---
type: "post"
stable_id: "post:agent-skills-at-organizational-scale"
slug: "agent-skills-at-organizational-scale"
title: "Hundreds Of Agent Skills Create A Lifecycle Problem, Not A Prompt Library"
description: "At organizational scale, skills need ownership, versioning, tests, progressive disclosure, permissions, deprecation, and evidence that the workflow still matches its tools."
retrieval_nugget: "A skill should encode a bounded job and load references or scripts only when needed. A large library needs catalog metadata, responsible owners, CI checks, usage evidence, review dates, and a retirement path."
published_at: "2026-08-04"
updated_at: "2026-08-06"
record_date: "2026-08-04"
date_kind: "published_at"
topics: ["agent-skills","knowledge-management","governance","progressive-disclosure","testing"]
entities: ["Agent Skills","PostHog","Addy Osmani"]
source_urls: ["https://github.com/addyosmani/agent-skills","https://github.com/posthog/skills","https://github.com/agentskills/agentskills"]
source_format: "github"
editorial_timing: {"lane":"regular_hourly","scheduled_at":"2026-08-07T17:00:00+03:00","real_news_delta":"owner-approved primary-source mechanism or merged analysis"}
visual_decision: {"status":"included","reason":"the central mechanism is a flow, loop, architecture, decision, or state transition that benefits from a diagram","reviewed_by":"codex"}
schema_version: "newruntime-agent-readable-v0.2"
status: "published"
visuals: [{"role":"hero","src":"/images/drip/agent-skills-at-organizational-scale/agent-skills-at-organizational-scale.webp","alt":"A whiteboard lifecycle loop showing an agent skill moving through cataloging, activation, execution evidence, owner review, update, and retirement.","caption":"New Runtime synthesis from Agent Skills and PostHog skills collection."}]
routes: {"html":"https://newruntime.com/posts/agent-skills-at-organizational-scale/","markdown":"https://newruntime.com/posts/agent-skills-at-organizational-scale.md","json":"https://newruntime.com/posts/agent-skills-at-organizational-scale.json"}
---

# Hundreds Of Agent Skills Create A Lifecycle Problem, Not A Prompt Library

## Retrieval answer

A skill should encode a bounded job and load references or scripts only when needed. A large library needs catalog metadata, responsible owners, CI checks, usage evidence, review dates, and a retirement path.

Agent Skills are becoming an operational knowledge layer rather than a collection of clever prompts. Addy Osmani's repository packages engineering workflows across define, plan, build, verify, review, and ship. PostHog maintains a separate skills collection with official, team, community, and meta categories. The interesting question begins when these libraries contain hundreds of entries.

Scale creates failure modes: overlapping triggers, stale tool names, undocumented permissions, procedures without owners, references that no longer match the product, and giant files that defeat progressive disclosure. A skill needs a bounded job-to-be-done, a narrow description for activation, versioned scripts or references, tests for the fragile steps, and an explicit human gate where judgment remains necessary.

The library itself needs lifecycle metadata: owner, last verified date, supported agents, required tools, risk class, usage, failures, replacement skill, and deprecation state. Progressive disclosure reduces context cost, but it does not maintain correctness. A skill store without review and retirement becomes another dependency registry with executable instructions.