plugin-home
Skill22 starsChanged 9 days agoMITView on GitHub
Scaffold a Home panel for an Ethos plugin — generates panel.tsx, wires build config, adds package.json exports
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dependency-analyzerSkill
- docsSkill
- handoffSkill
- openai-reviewerSkill
- schema-validatorSkill
- security-auditSkill
- session-auditSkill
- test-validatorSkill
- claude-codeSkill
- codexSkill
- opencodeSkill
- chartsSkill
- export-csvSkill
- export-excelSkill
- make-chartSkill
- make-html-reportSkill
- make-pdfSkill
- a2a-communicateSkill
- a2a-handle-inboundSkill
- codebase-inspectionSkill
- ethos-skill-authoringSkill
- native-mcpSkill
- github-authSkill
- github-code-reviewSkill
- github-issuesSkill
- github-pr-workflowSkill
- github-repo-managementSkill
- birth-ritualSkill
- get-to-know-youSkill
- xurlSkill
- arxivSkill
- grounded-citationsSkill
- research-paper-writingSkill
- reddit-researchSkill
- code-reviewSkill
- coding-agentSkill
- planSkill
- requesting-code-reviewSkill
- spikeSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- tddSkill
- writing-plansSkill
- no-ai-slopSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
Read the plugin's package.json to extract:
- Very specific: line 52
Update package.json with panel exports and peer deps
- Distinctive: line 54
Update build config for panel entry
- Very specific: line 56
Run npm run build to verify the panel compiles
- Distinctive: line 78
After generating, iterate with:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plugin Home Panel Scaffold
Generate a complete, working Home panel for an Ethos plugin.
When to use
- Building a new plugin that needs a visual dashboard
- Adding a Home panel to an existing plugin
- Learning the plugin panel API by example
Prerequisites
- Working plugin with
package.jsoncontaining anethosfield - At least one tool registered in the plugin
What this skill generates
src/panel.tsx— Complete React Home panel with:- Auth status check via
credentialPreview() - OAuth reconnect button via
requestOAuth() - Tool execution via
executeTool()with loading/error states - Theme-aware CSS using
var(--...)custom properties - Error boundary wrapper
- Auth status check via
package.jsonupdates:"hasHomePanel": truein theethosfield"./panel": { "import": "./dist/panel.js" }in exports"@ethosagent/ui-components": ">=0.x"in peerDependencies"dev:panel"script for watch mode
tsup.config.tsupdates:panelentry point added- React and ui-components marked as external
Workflow
- Read the plugin's
package.jsonto extract:- Plugin ID, name, description
- Credential schema from
ethos.credentials - Tool names from the plugin's registered tools
- Generate
src/panel.tsxusing the template, customized with:- Plugin-specific credential checks
- Tabs for each major tool group
- Summary metrics from the first tool
- Update
package.jsonwith panel exports and peer deps - Update build config for panel entry
- Run
npm run buildto verify the panel compiles
Panel structure
The generated panel follows this layout:
┌─────────────────────────────────────────┐
│ [Plugin Name] [Status badge] │
│ [Detail line + action button if needed] │
├─────────────────────────────────────────┤
│ [Metric] [Metric] [Metric] │
├─────────────────────────────────────────┤
│ [Tab A] [Tab B] [Tab C] │
│ ────────────────────────────────────── │
│ [Data content — loading skeleton │
│ or rendered tool result] │
└─────────────────────────────────────────┘Dev mode
After generating, iterate with:
npm run dev:panel # watches src/panel.tsx, rebuilds on changeDesktop app re-imports on each drawer open. Web serves fresh on each request.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

