Community infrastructure for extending Eagle — the creative asset manager.
This organization maintains plugins, a community index, developer tooling, and API specs that make up the Eagle plugin ecosystem.
power-eagle — A plugin that lets you write and run userscripts inside Eagle. Instead of building a full plugin, you can author lightweight scripts that automate Eagle tasks directly.
eagle-brat — A plugin manager. Browse the community index, see what is already installed, and install or update plugins without leaving Eagle.
eagle-template — Base template for new Eagle plugins. Ships with a lefthook-driven local devops workflow, a .eagleplus/ automation layer, and a single GitHub Actions workflow for packaging and releasing .eagleplugin archives.
eagle-react-template — React + Vite variant of the base template. Use this for plugins with a React UI.
eagle-i18n-template — Variant of the base template with i18n support wired in. Use this if your plugin targets multiple locales from the start.
eagle-spec — TypeScript declarations (eagle.d.ts) and Git-friendly HTTP request files for the Eagle Plugin and Web APIs. Reference this for type coverage and API exploration.
community-index — A GitOps-managed JSON registry of Eagle plugin releases. Automated workflows handle validation, version tracking, and scheduled refresh. Consumed directly by eagle-brat.
To add your plugin, open an Add Entry issue in that repository. To report a stale version, use the Mismatched Version issue form.
As a user: Install eagle-brat to browse and manage community plugins from inside Eagle. If you want to automate Eagle tasks without writing a full plugin, try power-eagle for userscript-based workflows.
As a plugin author: Use one of the template repos above to scaffold your plugin. Reference eagle-spec for type definitions, then submit to community-index when ready.
Each repository has its own contributing notes. In general: issues and pull requests are welcome, template and infrastructure repos follow the conventions in their .eagleplus/ directories, and the community index uses issue forms rather than direct PRs for plugin submissions.