Source profileQuality 65/100

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
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Use this plugin when the user asks for a live artifact that summarizes changing operational data.

Best for

    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

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    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.

    Source-detected install commandSource
    npx skills add https://github.com/nexu-io/open-design --skill "plugins/spec/examples/create-live-artifact-ops"
    Safe inspection promptEditorial

    Inspect the Agent Skill "create-live-artifact-ops" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/spec/examples/create-live-artifact-ops/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. 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

    1. 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.
    2. 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

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score65/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82,073SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guidecatalog recordEditorialGenerated 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
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    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

    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 affordances in the UI copy.
    5. Return index.html and 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.

    Alternatives

    Compare before choosing