agentleFS
ethosagentethosagent/ethos/.agents/skills/plugin-home/SKILL.md

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

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
  1. Very specific:

    Read the plugin's package.json to extract:

    line 42
  2. Very specific:

    Update package.json with panel exports and peer deps

    line 52
  3. Distinctive:

    Update build config for panel entry

    line 54
  4. Very specific:

    Run npm run build to verify the panel compiles

    line 56
  5. Distinctive:

    After generating, iterate with:

    line 78

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.json containing an ethos field
  • At least one tool registered in the plugin

What this skill generates

  1. 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
  2. package.json updates:
    • "hasHomePanel": true in the ethos field
    • "./panel": { "import": "./dist/panel.js" } in exports
    • "@ethosagent/ui-components": ">=0.x" in peerDependencies
    • "dev:panel" script for watch mode
  3. tsup.config.ts updates:
    • panel entry point added
    • React and ui-components marked as external

Workflow

  1. Read the plugin's package.json to extract:
    • Plugin ID, name, description
    • Credential schema from ethos.credentials
    • Tool names from the plugin's registered tools
  2. Generate src/panel.tsx using the template, customized with:
    • Plugin-specific credential checks
    • Tabs for each major tool group
    • Summary metrics from the first tool
  3. Update package.json with panel exports and peer deps
  4. Update build config for panel entry
  5. Run npm run build to 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 change

Desktop app re-imports on each drawer open. Web serves fresh on each request.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.