plugin-create

Guide developers through designing and implementing standards-compliant Engram enrichment plugins.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rnwolfe/engram --skill plugin-create-rnwolfe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-create
Source: https://github.com/rnwolfe/engram/tree/main/.claude/skills/plugin-create
Command: npx skills add https://github.com/rnwolfe/engram --skill plugin-create-rnwolfe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides interactive guidance to design, implement, and validate a standards-compliant Engram enrichment plugin, reducing risk of misconfiguration and drift.

Core Features & Use Cases

  • Stepwise guidance through six design phases (Intent, Transport, Contract surface, Scaffolding, Implementation, Testing) to ensure a complete plugin with manifest, entry points, and tests.
  • Evidence-first guidance that enforces Engram's contract, including proper auth, scope, cursor semantics, vocab alignment, and per-item ingestion patterns.
  • Templates, validation checks, and best practices for both in-repo js-module plugins and external executables.

Quick Start

Begin by answering the guided questions to generate a production-ready Engram plugin scaffold.

Frequently Asked Questions about plugin-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Engram enrichment plugin that passes manifest and vocabulary validation?

To create an Engram enrichment plugin, follow guided design phases covering intent, transport, contract surface, scaffolding, implementation, and testing to ensure manifest fields, entry points, and vocab extensions are fully validated.

What is the Engram plugin contract for auth, scope, and cursor semantics?

The Engram plugin contract requires proper auth configuration, scoped access, correct cursor semantics for pagination, per-item ingestion patterns, and vocab alignment to maintain standards compliance across enrichment plugins.

Can I build an external executable plugin instead of an in-repo js-module for Engram?

Yes, you can build either in-repo js-module plugins or external executable transports; both formats are supported with specific templates, validation checks, and best practices for scaffolding and implementation.

How do I scaffold tests for an Engram plugin covering edge and entity modeling?

Scaffold tests by following the testing design phase, which provides test scaffolding and validation checks across manifest fields, vocabulary extensions, and edge/entity modeling to ensure complete plugin coverage.

What's the best way to ensure frontmatter and manifest fields are present in a new plugin?

The best way to ensure frontmatter and manifest fields are present is using stepwise guided validation that enforces the Engram contract during the scaffolding and implementation phases of plugin design.

Why does my Engram enrichment plugin fail vocab alignment checks?

Vocab alignment checks fail when plugin vocabulary extensions do not match the Engram contract; the guided design process validates these extensions during the contract surface and testing phases to prevent drift.