convert-to-docker
- Repo stars 0
- Author updated Live
- Author repo nano-core
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 83 / 100 · community maintained
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Write / modify
- Env read
- Network behavior
- External requests
- 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，默认拥有全部工具权限。; 检出高风险片段：pipe_curl_to_shell
---
name: convert-to-docker
description: Normalize FFT_nano to Docker-first runtime defaults. Use when user asks for Docker parity, cross…
category: devops
runtime: Docker
---
# convert-to-docker output preview
## PART A: Task fit
- Use case: Normalize FFT_nano to Docker-first runtime defaults. Use when user asks for Docker parity, cross-platform setup, or to disable host runtime mode. This repository now supports two runtime modes: makes outbound network calls; runs on Docker. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “1. Verify Docker Is Installed and Running / 2. Set Docker Runtime Defaults / 3. Build Runtime Artifacts” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Normalize FFT_nano to Docker-first runtime defaults. Use when user asks for Docker parity, cross-platform setup, or to disable host runtime mode. This repository now supports two runtime modes: makes outbound network calls; runs on Docker. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “1. Verify Docker Is Installed and Running / 2. Set Docker Runtime Defaults / 3. Build Runtime Artifacts” 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, read environment variables; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files, read environment variables; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/bin`; use them first when your agent supports command triggers.
Provide inputs and boundaries
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, read environment variables.
Validate with a small run
Start with a small task and check whether the result follows “1. Verify Docker Is Installed and Running / 2. Set Docker Runtime Defaults / 3. Build Runtime Artifacts”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: convert-to-docker
description: Normalize FFT_nano to Docker-first runtime defaults. Use when user asks for Docker parity, cross…
category: devops
source: 0-CYBERDYNE-SYSTEMS-0/nano-core
---
# convert-to-docker
## When to use
- Normalize FFT_nano to Docker-first runtime defaults. Use when user asks for Docker parity, cross-platform setup, or to…
- 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 “1. Verify Docker Is Installed and Running / 2. Set Docker Runtime Defaults / 3. Build Runtime Artifacts” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; may access external network resources; 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. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "convert-to-docker" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 1. Verify Docker Is Installed and Running / 2. Set Docker Runtime Defaults / 3. Build Runtime Artifacts
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, write/modify files, read environment variables | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Convert to Docker (Current Runtime Policy)
This repository now supports two runtime modes:
docker(preferred/default)host(advanced, explicit opt-in)
This skill enforces Docker-first configuration and verifies the runtime end-to-end.
1. Verify Docker Is Installed and Running
docker --version
docker info >/dev/null && echo "Docker ready" || echo "Docker not ready"If Docker is missing:
- macOS: install Docker Desktop from https://www.docker.com/products/docker-desktop/
- Linux:
curl -fsSL https://get.docker.com | sh && sudo systemctl start docker
2. Set Docker Runtime Defaults
Update .env so Docker is selected and host-mode overrides are removed:
# ensure runtime is docker-first auto mode
if grep -q '^CONTAINER_RUNTIME=' .env 2>/dev/null; then
sed -i.bak 's/^CONTAINER_RUNTIME=.*/CONTAINER_RUNTIME=auto/' .env
else
echo 'CONTAINER_RUNTIME=auto' >> .env
fi
# remove host runtime opt-ins if present
sed -i.bak '/^FFT_NANO_ALLOW_HOST_RUNTIME=/d' .env
sed -i.bak '/^FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD=/d' .env3. Build Runtime Artifacts
./container/build.sh
npm run build4. Verify Agent Runtime
echo '{}' | docker run -i --entrypoint /bin/echo fft_nano-agent:latest "Container OK"5. Verify Setup Path
Run the project setup checker (Docker path):
bash scripts/setup.shExpected behavior:
- Detects Docker runtime
- Builds/uses Docker image
- Passes runtime smoke checks
6. Restart Service
launchctl kickstart -k gui/$(id -u)/com.fft_nanoNotes
- Do not set
CONTAINER_RUNTIME=hostunless explicitly requested. - Host mode is intentionally gated by
FFT_NANO_ALLOW_HOST_RUNTIME=1. - Docker is the supported default for parity and operational consistency.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review