pluto-pair
- Repo stars 301
- Author updated Live
- Author repo marketplace
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @aiskillstore · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: pluto-pair
description: Pair Codex with Pluto.jl notebooks using MCP tools. Use for discovering visible Pluto servers, a…
category: ai
runtime: no special runtime
---
# pluto-pair output preview
## PART A: Task fit
- Use case: Pair Codex with Pluto.jl notebooks using MCP tools. Use for discovering visible Pluto servers, attaching to running notebooks, opening notebooks headlessly, inspecting @bind controls, setting bond values, reading compact state, or exporting HTML..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Pair Codex with Pluto.jl notebooks using MCP tools. Use for discovering visible Pluto servers, attaching to running notebooks, opening notebooks headlessly, inspecting @bind controls, setting bond values, reading compact state, or exporting HTML.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: pluto-pair
description: Pair Codex with Pluto.jl notebooks using MCP tools. Use for discovering visible Pluto servers, a…
category: ai
source: aiskillstore/marketplace
---
# pluto-pair
## When to use
- Pair Codex with Pluto.jl notebooks using MCP tools. Use for discovering visible Pluto servers, attaching to running no…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "pluto-pair" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Pluto Pair
Use the pluto-pair MCP server when a task involves Pluto.jl notebook state or controls.
If the user has a Pluto browser window open, prefer live attach first:
pluto_discover_serversto check local Pluto servers, especially port 1234.pluto_attach_sessionto attach to a notebook already running in that visible server.pluto_open_visibleto open a notebook in the visible server and attach to it.
Live attached sessions update the same notebook the user sees in their browser.
Use headless tools for isolated checks, CI-like validation, exports, or untrusted/static previews:
pluto_list_notebooksto discover notebook files.pluto_open_notebookto open and execute a trusted notebook. Execution is the default; passexecution_allowed=falseonly for untrusted preview.pluto_list_bondsto inspect@bindvariables.pluto_set_bondsto set bound values and trigger Pluto reactivity.pluto_read_stateto summarize code, outputs, errors, logs, and bonds.pluto_export_htmlto write a rendered HTML export.pluto_close_notebookwhen finished. On live attached sessions, this only detaches and does not shut down the user's Pluto notebook.
Use browser automation only for visual smoke checks or screenshots.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review