Goal: - Show the user the available high-level start parameters for Co-Scientist. When to use: - The user asks what knobs or parameters are available. - The user asks how `/co-scientist-start` can be configured. - The user wants the expert-facing parameter table instead of the short guided intake. Execution steps: 1. Run: ```bash python -m tools.host.claude_project_cli params ``` 2. If the user explicitly wants machine-readable output, run: ```bash python -m tools.host.claude_project_cli para...
Scanned 9/7/2026
Install to Claude Code
npx -y skills add panjose/Co-Scientist --skill co-scientist-params --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Co Scientist Params?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/panjose-co-scientist-params)More formats (shields.io, HTML) on the badges page.
# co-scientist-params
Goal:
- Show the user the available high-level start parameters for Co-Scientist.
When to use:
- The user asks what knobs or parameters are available.
- The user asks how `/co-scientist-start` can be configured.
- The user wants the expert-facing parameter table instead of the short guided intake.
Execution steps:
1. Run:
```bash
python -m tools.host.claude_project_cli params
```
2. If the user explicitly wants machine-readable output, run:
```bash
python -m tools.host.claude_project_cli params --format json
```
3. Present the parameter surface in this order:
- core axes
- advanced axes
- utility flags only when relevant
4. Use `../../shared-references/start-parameters.md` as the canonical contract for names, defaults, and meanings.
Rules:
- Lead with the core axes and defaults rather than dumping every possible flag immediately.
- Do not expose low-level mechanics settings such as `num_debaters`, `elo_k_factor`, or `ucb_exploration_constant` as user-facing start parameters.
- If the user only wants to begin a run, route back to `/co-scientist-start` after answering the parameter question.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling