Source profileQuality 64/100

nexu-io/open-design/plugins/spec/examples/deploy-vercel-static/SKILL.md

deploy-vercel-static

Use this plugin when the user wants to deploy an accepted static web artifact to Vercel or prepare an equivalent deployment handoff with preview and production URLs.

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 wants to deploy an accepted static web artifact to Vercel or prepare an equivalent deployment handoff with preview and production URLs.

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/deploy-vercel-static"
    Safe inspection promptEditorial

    Inspect the Agent Skill "deploy-vercel-static" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/spec/examples/deploy-vercel-static/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. Confirm the artifact path, project name, and whether this is preview-only or production. 2. Validate that the artifact can run as a static web surface. 3. Prepare deployment files if needed. 4. Ask for confirmation before deployment. 5. Deploy or produce exact deployment inst…

      Confirm the artifact path, project name, and whether this is preview-only or production.Validate that the artifact can run as a static web surface.Prepare deployment files if needed.
    2. 02

      Output Contract

      Produce deploy-summary.md and a preview URL, production URL, or prepared command list.

      Produce deploy-summary.md and a preview URL, production URL, or prepared command list.

    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 score64/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/deploy-vercel-static/SKILL.md
    Commit
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Deploy Vercel Static

    Workflow

    1. Confirm the artifact path, project name, and whether this is preview-only or production.
    2. Validate that the artifact can run as a static web surface.
    3. Prepare deployment files if needed.
    4. Ask for confirmation before deployment.
    5. Deploy or produce exact deployment instructions and return links.

    Output Contract

    Produce deploy-summary.md and a preview URL, production URL, or prepared command list.

    Alternatives

    Compare before choosing