Agent Plugin Templates: Forkable Starters for High-Intent Use Cases

SEO learn content is useful, but templates convert better. Start from a working plugin shape, fork it into your own repo, customize the operating model, run smoke evals, and publish it with Telvine.

Fork this into your own plugin: Agent Plugin Templates on GitHub

npm i -g telvine
telvine login
telvine publish ./my-plugin

Template loop

Each starter is built around a high-intent job, a concrete SKILL.md, a Codex-style .codex-plugin/plugin.json, a domain operating model, connector contract, smoke eval suite, and a safe telemetry policy. The CTA is not "read more." The CTA is: fork this into your own plugin.

Template	What it helps users do	GitHub path
Gmail triage plugin	Prioritize inboxes, extract reply queues, and summarize waiting-on threads.	plugins/gmail-triage-plugin
Slack support plugin	Turn support channels into owner, severity, status, and next-action queues.	plugins/slack-support-plugin
Browser automation plugin	Run repeatable website checks, QA flows, and browser operations.	plugins/browser-automation-plugin
PDF review plugin	Extract obligations, issues, page references, and approval notes from PDFs.	plugins/pdf-review-plugin
Spreadsheet reporting plugin	Convert CSV/XLSX inputs into repeatable reports, anomaly checks, and summaries.	plugins/spreadsheet-reporting-plugin
Internal ops plugin	Review exceptions, blocked work, handoffs, and operational risk.	plugins/internal-ops-plugin
CRM enrichment plugin	Enrich accounts and contacts while flagging missing or uncertain fields.	plugins/crm-enrichment-plugin
Code review plugin	Review pull requests for bugs, regressions, missing tests, and release risk.	plugins/code-review-plugin

What every template includes

• A .codex-plugin/plugin.json manifest with stable plugin identity, discovery copy, default prompts, and publish-ready metadata.
• A focused SKILL.md capability that tells the agent when to load the workflow and how to complete it.
• A references/operating-model.md file with domain taxonomies, prioritization rules, output fields, and guardrails.
• A connectors/README.md contract for the source systems and write-approval boundaries the plugin expects.
• An evals/smoke-cases.json suite that gives Telvine and CI a starting quality gate.
• A README with the Telvine publish loop:

npm i -g telvine
telvine login
telvine publish ./my-plugin

• Metadata-only telemetry guidance using skill.invocation.* for Skills and plugin.component.invoked / plugin.component.error for non-Skill behavior.

How to use one

1. Fork rforgeon/agent-plugin-templates.
2. Copy the template folder that matches your use case.
3. Rename the plugin, update prompts, and replace the Skill workflow with your domain-specific operating rules.
4. Wire your connector, tune the operating model, and adapt the smoke evals.
5. Publish the plugin:

npm i -g telvine
telvine login
telvine publish ./my-plugin

Why this works for SEO

People searching for "Gmail triage plugin," "Slack support agent," "PDF review AI plugin," or "code review agent plugin" are closer to build intent than readers looking for abstract definitions. A forkable starter lets them start with a concrete plugin product and then instrument, evaluate, and improve it with Telvine.

Fork the repo, make one starter yours, and ship a plugin users can install.