Apple Container Test Runner
RustPython/RustPython
Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.
Covers bringing up and runtime-testing the claude-command-center dashboard server on Linux, including duplicate instances and fresh-install checks.
Install CCC Dashboard Runtime Testing
$ npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install amirfish1/claude-command-center testing-ccc-dashboard --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/amirfish1/claude-command-center.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing-ccc-dashboard .claude/skills/testing-ccc-dashboard && rm -rf skills-srcUse ~/.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/
Install the "testing-ccc-dashboard" agent skill from https://github.com/amirfish1/claude-command-center/tree/main/.agents/skills/testing-ccc-dashboard into .claude/skills/testing-ccc-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ccc-dashboard", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/amirfish1/claude-command-center/tree/main/.agents/skills/testing-ccc-dashboardType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install amirfish1/claude-command-center testing-ccc-dashboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amirfish1/claude-command-center.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/testing-ccc-dashboard .agents/skills/testing-ccc-dashboard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing-ccc-dashboard" agent skill from https://github.com/amirfish1/claude-command-center/tree/main/.agents/skills/testing-ccc-dashboard into .agents/skills/testing-ccc-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ccc-dashboard", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install amirfish1/claude-command-center testing-ccc-dashboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amirfish1/claude-command-center.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/testing-ccc-dashboard .cursor/skills/testing-ccc-dashboard && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "testing-ccc-dashboard" agent skill from https://github.com/amirfish1/claude-command-center/tree/main/.agents/skills/testing-ccc-dashboard into .cursor/skills/testing-ccc-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ccc-dashboard", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/amirfish1/claude-command-center.git --path .agents/skills/testing-ccc-dashboard--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install amirfish1/claude-command-center testing-ccc-dashboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amirfish1/claude-command-center.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/testing-ccc-dashboard .gemini/skills/testing-ccc-dashboard && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "testing-ccc-dashboard" agent skill from https://github.com/amirfish1/claude-command-center/tree/main/.agents/skills/testing-ccc-dashboard into .gemini/skills/testing-ccc-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ccc-dashboard", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install amirfish1/claude-command-center testing-ccc-dashboardInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/amirfish1/claude-command-center.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/testing-ccc-dashboard .github/skills/testing-ccc-dashboard && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "testing-ccc-dashboard" agent skill from https://github.com/amirfish1/claude-command-center/tree/main/.agents/skills/testing-ccc-dashboard into .github/skills/testing-ccc-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ccc-dashboard", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install amirfish1/claude-command-center testing-ccc-dashboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amirfish1/claude-command-center.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/testing-ccc-dashboard .opencode/skills/testing-ccc-dashboard && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "testing-ccc-dashboard" agent skill from https://github.com/amirfish1/claude-command-center/tree/main/.agents/skills/testing-ccc-dashboard into .opencode/skills/testing-ccc-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ccc-dashboard", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
testing-ccc-dashboard- GitHub stars
- 178
- Token cost
- ~1.1k tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Covers bringing up and runtime-testing the claude-command-center dashboard server on Linux, including duplicate instances and fresh-install checks.
- Bringing up the CCC dashboard for manual or automated testing
- SKILL.md covers Bringing up instances, Browser verification, Fresh-install simulation and Forcing a [ccc:swallowed] line, plus 3 more sections
- Calls python3, git and node
- Running a before/after comparison of two dashboard instances
What it does
The server needs no virtual environment or npm install, just a direct Python invocation with port, bind-host and ephemeral-mode environment variables set; a before/after pair of instances for the same repository needs both an ephemeral flag and a duplicate-repo-allow flag, since the server otherwise refuses a second instance of the same repo across worktrees. Startup takes roughly 15 to 25 seconds before the port answers, so polling with curl is preferred over a fixed sleep, and a crashed earlier process can silently hold the port, which a socket check and a kill clears.
Browser verification uses the repo's own puppeteer-based snapshot script rather than Playwright, falling back to a real Chrome driven by computer-use when puppeteer's browser isn't downloaded on a fresh machine; the first load shows a telemetry modal, a product tour and an install toast that all need dismissing. A fresh-install simulation either uses a machine with no existing Claude projects folder, or points the home directory at an empty temporary one, noting that it must be writable at import time since the server creates its own folder and a SQLite store there.
When your agent uses it
- Bringing up the CCC dashboard for manual or automated testing
- Running a before/after comparison of two dashboard instances
- Simulating a fresh install to test first-run behavior
Example prompts
- “Start two CCC dashboard instances so I can compare before and after.”
- “Simulate a fresh install of the dashboard and check the first-run screens.”
- “The dashboard port isn't responding, help me debug the startup.”
Requirements
- Python 3 (standard library only)
- A Linux box with Chrome or puppeteer's bundled browser
What it can do on your machine
Read from SKILL.md and the folder at commit a0d2e91. 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
Shell commands in SKILL.md call:
python3gitnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
CCC Dashboard Runtime Testing loads about 1.1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 495 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 495 words (~1,121 tokens).
“Stdlib-only; no venv or npm install needed to run the server.”
- name
- testing-ccc-dashboard
Files
Just SKILL.md in .agents/skills/testing-ccc-dashboard of amirfish1/claude-command-center.
Open the folder on GitHubat commit a0d2e91
Compare with similar skills
CCC Dashboard Runtime Testing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CCC Dashboard Runtime Testing this skillamirfish1/claude-command-center | 178 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Apple Container Test RunnerRustPython/RustPython | 22k | — | ~467 | Automated safety check: Pass | MIT | |
| Fake Model Provider Faultsdifferent-ai/openwork | 24k | — | ~642 | Automated safety check: Pass | Custom licence | |
| Agentacct Workflowmikehasa/agentacct | 766 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Brightdata Proxybrightdata/skills | 264 | — | ~5.1k | Automated safety check: Pass | MIT | |
| Abx DlArchiveBox/abx-dl | 145 | — | ~557 | Automated safety check: Pass | MIT |
Similar skills
Fake Model Provider Faults
different-ai/openwork
Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.
Agentacct Workflow
mikehasa/agentacct
A skill your agent uses when working in a repo with agentacct MCP configured, or when asked to track coding-agent work, smoke-test agentacct integrations, or report objective AI-agent task evidence.
Brightdata Proxy
brightdata/skills
Generate working code that routes HTTP requests through Bright Data proxy networks (Datacenter, ISP, Residential, Mobile) and help users decide which network and IP pool type to use (shared pool…
Abx Dl
ArchiveBox/abx-dl
Use this when working on the standalone ArchiveBox downloader CLI, extractor orchestration, plugin execution, config, and output verification.
Pipensx Bug Report Triage
i3sey/pipensx
Decodes QR-code bug report photos and screenshots from the pipensx app into a log, then triages crashes and update, download or install failures.
More from amirfish1/claude-command-center
CCC Token Throughput
amirfish1/claude-command-center
Answers token usage and cost questions from the Claude Command Center throughput dashboard and shares its link, for the last 7 days or one session.
Related
Categories
Questions about CCC Dashboard Runtime Testing
What does CCC Dashboard Runtime Testing do?
Covers bringing up and runtime-testing the claude-command-center dashboard server on Linux, including duplicate instances and fresh-install checks. The server needs no virtual environment or npm install, just a direct Python invocation with port, bind-host and ephemeral-mode environment variables set; a before/after pair of instances for the same repository needs both an ephemeral flag and a duplicate-repo-allow flag, since the server otherwise refuses a second instance of the same repo across worktrees. Startup takes roughly 15 to 25 seconds before the port answers, so polling with curl is preferred over a fixed sleep, and a crashed earlier process can silently hold the port, which a socket check and a kill clears.
When should I use CCC Dashboard Runtime Testing?
CCC Dashboard Runtime Testing fits situations like: bringing up the CCC dashboard for manual or automated testing; running a before/after comparison of two dashboard instances; simulating a fresh install to test first-run behavior.
How do I install CCC Dashboard Runtime Testing in Claude Code?
Run `npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a claude-code`. Or copy the skill folder (.agents/skills/testing-ccc-dashboard in amirfish1/claude-command-center) into .claude/skills/testing-ccc-dashboard in your project. Claude Code loads it when a task matches its description.
How do I install CCC Dashboard Runtime Testing in Codex?
Run `npx skills add amirfish1/claude-command-center --skill testing-ccc-dashboard -a codex`. Or copy the skill folder (.agents/skills/testing-ccc-dashboard in amirfish1/claude-command-center) into .agents/skills/testing-ccc-dashboard in your project. Codex loads it when a task matches its description.
Can I use CCC Dashboard Runtime Testing 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 amirfish1/claude-command-center --skill testing-ccc-dashboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-ccc-dashboard, .gemini/skills/testing-ccc-dashboard, .github/skills/testing-ccc-dashboard and .opencode/skills/testing-ccc-dashboard in your project.
What does CCC Dashboard Runtime Testing need to run?
Going by SKILL.md and its folder, CCC Dashboard Runtime Testing needs the command-line tools its instructions call (python3, git and node). Our summary lists: Python 3 (standard library only); A Linux box with Chrome or puppeteer's bundled browser.
Does CCC Dashboard Runtime Testing access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is CCC Dashboard Runtime Testing 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 CCC Dashboard Runtime Testing use?
CCC Dashboard Runtime Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does CCC Dashboard Runtime Testing use?
About 1.1k tokens (SKILL.md is roughly 4.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 CCC Dashboard Runtime Testing?
Skills that share tags, products or a category with CCC Dashboard Runtime Testing: Apple Container Test Runner (RustPython/RustPython, 22k stars), Fake Model Provider Faults (different-ai/openwork, 24k stars), Agentacct Workflow (mikehasa/agentacct, 766 stars) and Brightdata Proxy (brightdata/skills, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CCC Dashboard Runtime Testing?
amirfish1 (a GitHub user) maintains it in amirfish1/claude-command-center, which has 178 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.
Source: amirfish1/claude-command-center on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.