Create Plugin Agent Skill

by DataDog

Scaffold a new datadog-ci plugin end-to-end using repository conventions.

440 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

161

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/DataDog/datadog-ci --skill create-plugin

The instruction itself

3 sections, as written by the author

Create Plugin

Scaffold a new datadog-ci plugin end-to-end. Walk the user through each step, confirming the scope name and whether the plugin should be built-in or separately installable.

Workflow

Ask for the scope name (kebab-case) and whether this is a built-in or separately installable plugin.

Run yarn plugin:create <scope> to scaffold packages/plugin-<scope>/.

Create the base command in packages/base/src/commands/<scope>/<command>.ts:
Extend BaseCommand from @datadog/datadog-ci-base
Use Command.Usage() for description
Use Option.* from clipanion for arguments/flags
execute() should call return executePluginCommand(this)
Export the command class

Create packages/base/src/commands/<scope>/cli.ts exporting a commands array containing the command class.

Create the plugin implementation in packages/plugin-<scope>/src/commands/<command>.ts:
Import and extend the base command
Implement the actual execute() logic
Return 0 for success

Update project files per the CONTRIBUTING.md checklist:
Add to .github/CODEOWNERS under the correct product
Add scope to the Usage section in root README.md
If new product: create a GitHub label, update pr-required-labels.yml, advanced-issue-labeler.yml, and release.yml changelog config

Notes

The commands map in packages/base/src/cli.ts is auto-generated by bin/lint-packages.ts -- do not edit it manually. Run yarn lint:packages to verify.
Use getRequestBuilder() or httpRequest() from base helpers for HTTP, not raw fetch or axios.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take datadog/create-plugin from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.