New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cockpit Rendering

by jianzhichun in jianzhichun/emerge

A skill your agent uses when designing or revising Emerge cockpit presentation, summaries, filters, action labels, or empty/error states without changing the HTTP API contract.

MITAuto-check passedBackend & APIs

Install Cockpit Rendering

skills CLI
$ npx skills add jianzhichun/emerge --skill cockpit-rendering -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jianzhichun/emerge cockpit-rendering --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jianzhichun/emerge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cockpit-rendering .claude/skills/cockpit-rendering && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cockpit-rendering
GitHub stars
104
Token cost
~387 tokens
SKILL.md length
184 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when designing or revising Emerge cockpit presentation, summaries, filters, action labels, or empty/error states without changing the HTTP API contract.

  • Revising Emerge cockpit presentation
  • SKILL.md covers Purpose, Rendering Principles, Empty States and Action Labels
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Empty/error states without changing the HTTP API contract

What it does

Cockpit Rendering is an agent skill from jianzhichun/emerge. Use when designing or revising Emerge cockpit presentation, summaries, filters, action labels, or empty/error states without changing the HTTP API contract.

Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering REST APIs. The licence is MIT.

When your agent uses it

  • Revising Emerge cockpit presentation
  • Empty/error states without changing the HTTP API contract

Example prompts

  • “/cockpit-rendering”

What it can do on your machine

Read from SKILL.md and the folder at commit 035db30. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cockpit Rendering loads about 387 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 184 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~387

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jianzhichun/emerge at commit 035db30, republished under its MIT licence (© jianzhichun). 184 words, ~387 tokens.

Download SKILL.mdSave it as .claude/skills/cockpit-rendering/SKILL.md (or your agent's skills folder).
name
cockpit-rendering
description
Use when designing or revising Emerge cockpit presentation, summaries, filters, action labels, or empty/error states without changing the HTTP API contract.

Cockpit Rendering

Purpose

Keep cockpit code focused on serving state and validating actions. Put presentation judgment here: what sections matter, how to label them, and how to keep the operator focused on flywheel progress.

Rendering Principles

  • Lead with actionable flywheel state: stable pipelines, canary risks, blocked synthesis, runner health.
  • Treat cockpit copy as operator guidance, not implementation truth. Source data still comes from /api/* and resources.
  • Do not invent new API fields. If a view needs data, first check existing endpoints and only propose API expansion explicitly.
  • Prefer short status labels over narrative prose in tables and cards.
  • Expose confidence and verification state when a recommendation could trigger operator action.

Empty States

  • No stable intents: explain that repeated successful spans are needed before zero-inference execution appears.
  • No runners: point to admin-runner-operations or runner-install-url instead of embedding long setup flow in code.
  • Synthesis blocked: show the reason and the latest sample/job ID so the operator can inspect the right artifact.

Action Labels

Use verb-first labels: Freeze policy, Resume policy, Open runner, Resolve conflict, Retry synthesis. Avoid labels that imply human approval gates for auto-promoted paths.

© jianzhichun, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cockpit-rendering of jianzhichun/emerge.

Open the folder on GitHubat commit 035db30

Compare with similar skills

Cockpit Rendering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cockpit Rendering compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cockpit Rendering this skilljianzhichun/emerge104—~387Automated safety check: PassMIT
Paperclippaperclipai/paperclip99k—~9.6kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
OpenAPI to MCP Servermcp-use/mcp-use11k—~5.2kAutomated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT

Similar skills

  • Paperclip

    paperclipai/paperclip

    Interact with the Paperclip control plane API for task coordination and governance.

    99k GitHub stars~9.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed

  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed

  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed

  • RuView CLI, API and WASM

    ruvnet/RuView

    Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.

    97k GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check: notes

More from jianzhichun/emerge

All 14 skills in this repo

  • Distilling Operator Flows

    jianzhichun/emerge

    A skill your agent uses when wiring a generic connector to capture remote operator actions and convert repeated event facts into pending pipeline work through Claude Code skills.

    104 GitHub stars~432 tokensUpdated 5 mo ago
    Auto-check passed

  • Emerge Forward Synthesis

    jianzhichun/emerge

    Distill Emerge forward flywheel WAL samples into a parameterized pipeline result.

    104 GitHub stars~585 tokensUpdated 5 mo ago
    Auto-check passed

  • Emerge Reverse Synthesis

    jianzhichun/emerge

    Distill Emerge reverse flywheel raw operator events into a structured synthesis result.

    104 GitHub stars~451 tokensUpdated 5 mo ago
    Auto-check passed

  • Initializing Vertical Flywheel

    jianzhichun/emerge

    A skill your agent uses when a user asks to initialize a domain flywheel from natural language context, especially when environment details are incomplete or mixed with execution assumptions.

    104 GitHub stars~2.2k tokensUpdated 5 mo ago
    Auto-check passed

  • Operator Monitor Debug

    jianzhichun/emerge

    A skill your agent uses when the operator monitoring pipeline appears broken: EventBus has no events, PatternDetector is not firing, elicitation dialog never appears, or OperatorMonitor is silent.

    104 GitHub stars~1k tokensUpdated 5 mo ago
    Auto-check passed

  • Policy Optimization

    jianzhichun/emerge

    A skill your agent uses when policy health needs tuning: too many explore pipelines, repeated failures, stalled promotions, or noisy rollback behavior.

    104 GitHub stars~916 tokensUpdated 5 mo ago
    Auto-check passed

Categories

Questions about Cockpit Rendering

What does Cockpit Rendering do?

A skill your agent uses when designing or revising Emerge cockpit presentation, summaries, filters, action labels, or empty/error states without changing the HTTP API contract. Cockpit Rendering is an agent skill from jianzhichun/emerge. Use when designing or revising Emerge cockpit presentation, summaries, filters, action labels, or empty/error states without changing the HTTP API contract.

When should I use Cockpit Rendering?

Cockpit Rendering fits situations like: revising Emerge cockpit presentation; empty/error states without changing the HTTP API contract.

How do I install Cockpit Rendering in Claude Code?

Run `npx skills add jianzhichun/emerge --skill cockpit-rendering -a claude-code`. Or copy the skill folder (skills/cockpit-rendering in jianzhichun/emerge) into .claude/skills/cockpit-rendering in your project. Claude Code loads it when a task matches its description.

How do I install Cockpit Rendering in Codex?

Run `npx skills add jianzhichun/emerge --skill cockpit-rendering -a codex`. Or copy the skill folder (skills/cockpit-rendering in jianzhichun/emerge) into .agents/skills/cockpit-rendering in your project. Codex loads it when a task matches its description.

Can I use Cockpit Rendering in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jianzhichun/emerge --skill cockpit-rendering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cockpit-rendering, .gemini/skills/cockpit-rendering, .github/skills/cockpit-rendering and .opencode/skills/cockpit-rendering in your project.

What does Cockpit Rendering need to run?

SKILL.md names no scripts, command-line tools or credentials: Cockpit Rendering is instructions for the agent only.

Does Cockpit Rendering access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cockpit Rendering safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cockpit Rendering use?

Cockpit Rendering is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cockpit Rendering use?

About 387 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cockpit Rendering?

Skills that share tags, products or a category with Cockpit Rendering: Paperclip (paperclipai/paperclip, 99k stars), Nodejs Backend Patterns (ever-works/ever-works, 162 stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and Use Yaak (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cockpit Rendering?

jianzhichun (a GitHub user) maintains it in jianzhichun/emerge, which has 104 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on April 26, 2026.

Source: jianzhichun/emerge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.