plugin-manifest-schema
Define plugin manifest schema with versioning and dependency declarations.
npx skills add a5c-ai/babysitter --skill plugin-manifest-schema --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Plugin Manifest Schema Define plugin manifest schema. ## Generated Patterns ```typescript import { z } from 'zod'; export const pluginManifestSchema = z.object({ name: z.string().regex(/^[a-z0-9-]+$/), version: z.string().regex(/^\d+\.\d+\.\d+/), description: z.string(), main: z.string().default('index.js'), author: z.string().optional(), license: z.string().optional(), engines: z.object({ app: z.string().optional(), node: z.string().optional(), }).optional(), dependencies: z.record(z.string()).optional(), hooks: z.array(z.string()).optional(), permissions: z.array(z.string()).optional(), }); export type PluginManifest = z.infer<typeof pluginManifestSchema>; ``` ## Target Processes - plugin-architecture-implementation
- Generated Patterns
- Target Processes
What does the plugin-manifest-schema skill do?
Define plugin manifest schema with versioning and dependency declarations.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill plugin-manifest-schema --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.