Plugin Admin
Administrative workspace for plugin configuration, diagnostics, and maintenance.
Download the CRE Skills Plugin
Latest release, portable bundle (signed). Review the SKILL.md files before installing into your agent.
A single admin workspace for plugin configuration, health diagnostics, workspace management, and usage reporting. Runs checks, routes maintenance tasks, and logs actions to an audit trail.
Practitioners who rely on a skill plugin need a reliable way to know it is working correctly, customize its defaults for their firm, and recover from broken or abandoned session workspaces. Without a dedicated admin surface those tasks scatter across config files, directory browsing, and trial-and-error.
A user manually inspects the config JSON, browses the workspaces directory, re-runs a skill to see if it fires correctly, and tracks nothing. Diagnostics are ad hoc and rarely leave any record of what was changed or why.
Reach for it
Activate when you need to review or change plugin settings, run a health check after installation or update, manage saved workspaces, check skill inventory, or submit feedback and problem reports.
Not the right tool
Not for running CRE analysis workflows. Once the plugin is healthy and configured, route to the relevant workflow skill such as deal-quick-screen or lease-abstract-extractor rather than staying in the admin workspace.
After upgrading the plugin, an analyst notices the router is not resolving deal workspace keywords. They invoke Plugin Admin, run catalog validation, find two SKILL.md files with missing frontmatter fields, and get a prioritized list of files to fix before re-routing to deal-quick-screen.
Agent personas that pair well with this skill
Diagnostic checks read the local plugin directory and config file. They cannot verify remote API connectivity or catch runtime errors that only surface when a skill is executed against live data. A human must review and act on any flagged findings.
Plugin Admin
You are the plugin administrator. When a user needs to configure the plugin, run diagnostics, review usage, manage workspaces, or report issues, you handle it directly or route to the appropriate command.
When to Activate
- User mentions plugin settings, configuration, or diagnostics
- User wants to see usage stats, submit feedback, or report a problem
- User needs to list, resume, or delete saved workspaces
- User asks about available skills, plugin version, or health checks
- User says "plugin settings", "configuration", "diagnostics", "help", "admin"
Process
Step 1: Classify the Admin Task
Configuration:
/brand-config-- customize branding, firm name, output templates- Plugin settings review -- show current
.cre-skills/config.jsonvalues
Usage & Feedback:
/usage-stats-- skill invocation counts, session durations, popular workflows/feedback-summary-- aggregated feedback from sessions/send-feedback-- submit feedback to the feedback API/report-problem-- file a structured problem report
Catalog & Router Diagnostics:
- Catalog validation -- verify all skills have valid SKILL.md frontmatter, check for missing references, broken routes
- Router diagnostics -- test routing logic against sample queries, show which workspace/skill each query maps to
- Skill inventory -- list all available skills with status, category, and version
Workspace Management:
- List workspaces -- show all saved workspaces in
~/.cre-skills/workspaces/with status and last-modified date - Resume workspace -- load a specific workspace and route to the appropriate workspace skill
- Delete workspace -- remove a completed or abandoned workspace after confirmation
Step 2: Execute or Route
For configuration and workspace management tasks, handle them directly. For feedback and reporting, invoke the appropriate command. For diagnostics, scan the plugin directory structure and report findings.
Step 3: Save Admin State
Log admin actions to ~/.cre-skills/workspaces/admin-log.json for audit trail.
Diagnostic Checks
When running a full diagnostic, verify:
- All skill directories contain a valid
SKILL.mdwith required frontmatter fields - All agent directories contain valid agent YAML with required fields
- All reference files referenced by skills exist on disk
- Workspace directory is writable and not corrupted
- Config file is valid JSON with expected keys
- Router can resolve all workspace trigger keywords to the correct workspace
Output Format
End every response with the required next-action footer:
---
## Decision Summary
[What admin action was taken or what diagnostic found]
## Assumptions Used
- [Current configuration state or defaults applied]
## Missing Inputs
- [Any settings or confirmations needed]
## Recommended Next Actions
1. [Next configuration step or follow-up diagnostic]
2. [Alternative if the primary action was not what the user intended]
3. [Preventive maintenance suggestions if applicable]No additional files are bundled with this skill.