nexu-io/open-design/plugins/spec/examples/create-live-artifact-ops/SKILL.md
create-live-artifact-ops
Create a refreshable live operations artifact for customer success, support, or launch review workflows.
- Source repository stars
- 91,167
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-25
- Source checked
- 2026-08-25
Decision brief
What it does: where it fits
Use this plugin when the user asks for a live artifact that summarizes changing operational data.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/nexu-io/open-design --skill "plugins/spec/examples/create-live-artifact-ops"Inspect the Agent Skill "create-live-artifact-ops" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/plugins/spec/examples/create-live-artifact-ops/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Workflow
1. Identify the source system or choose a mock source when no connector is available. 2. Define the artifact schema: KPIs, freshness, feed items, and owner actions. 3. Create a self-contained HTML artifact that renders a useful seeded state. 4. Include stale and refresh affordan…
Identify the source system or choose a mock source when no connector is available.Define the artifact schema: KPIs, freshness, feed items, and owner actions.Create a self-contained HTML artifact that renders a useful seeded state. - 02
Quality Checks
The artifact still works with seeded mock data.
The artifact still works with seeded mock data.Freshness and source status are visible.The user can tell what action to take next.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 65/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 91,167 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- nexu-io/open-design
- Skill path
- plugins/spec/examples/create-live-artifact-ops/SKILL.md
- Commit
- edfa6b5f447e95cb120eae030f03baba00dc34de
- License
- Apache-2.0
- Collected
- 2026-08-25
- Default branch
- main
View the original SKILL.md
Example Live Ops Artifact
Use this plugin when the user asks for a live artifact that summarizes changing operational data.
Workflow
- Identify the source system or choose a mock source when no connector is available.
- Define the artifact schema: KPIs, freshness, feed items, and owner actions.
- Create a self-contained HTML artifact that renders a useful seeded state.
- Include stale and refresh affordances in the UI copy.
- Return
index.htmland note which connector can be wired later.
Quality Checks
- The artifact still works with seeded mock data.
- Freshness and source status are visible.
- The user can tell what action to take next.
- The layout remains useful when values change.
Frequently asked questions
What to verify before installation and use
How do I install create-live-artifact-ops?
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/spec/examples/create-live-artifact-ops". Inspect the command and pinned source before running it.
Alternatives
Compare before choosing
garrytan/gbrain
bulk-ingestion
End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.
alirezarezvani/claude-skills
app-store-optimization
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
citation-audit
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
prowler-cloud/prowler
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance