fft setup
- Repo stars 0
- Author repo nano-core
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Node.js · Docker
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# fft-setup
Host prereq checker for nano-core.
## When to use this skill
- Use when an operator asks "can I run nano-core on this machine" or "what's missing".
- Use when a first-run setup fails and the cause is unclear.
## When not to use this skill
- Do not use for general node/npm installation help — link the user to upstream docs.
## Guardrails
- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Main/admin chat only for privileged actions.
- Read-only diagnostic: do not install or upgrade anything.
## Workflow
1. Run `bash scripts/check-prereqs.sh` from the operator's checkout root.
2. Report which prereqs are missing (if any).
3. If the only failure is the container runtime, suggest Docker install steps or the `NANO_CORE_ALLOW_HOST_RUNTIME=1` env override (set explicitly, never default).
Sections and files
Listed in source order.
sections -> When to use this skill → When not to use this skill → Guardrails → Workflow
terms -> Host prereq checker for nano-core. · - Use when an operator asks "can I run nano-core on this machine" or "what's missing". · - Do not use for general node/npm installation help — link the user to upstream docs. · - Never run destructive git commands unless explicitly requested. · 1. Run bash scripts/check-prereqs.sh from the operator's checkout root.
files/cmd -> bash scripts/check-prereqs.sh · NANO_CORE_ALLOW_HOST_RUNTIME=1 · node/npm · Main/admin · scripts/check-prereqs.sh
body sha256 -> 81b5601efef3
When to use this skill
Use when an operator asks "can I run nano-core on this machine" or "what's missing". Use when a first-run setup fails and the cause is unclear.
When not to use this skill
Do not use for general node/npm installation help — link the user to upstream docs.
Guardrails
Never run destructive git commands unless explicitly requested. Preserve unrelated worktree changes. Main/admin chat only for privileged actions. Read-only diagnostic: do not install or upgrade anything.
Workflow
Run
bash scripts/check-prereqs.shfrom the operator's checkout root. Report which prereqs are missing (if any). If the only failure is the container runtime, suggest Docker install steps or theNANO_CORE_ALLOW_HOST_RUNTIME=1env override (set explicitly, never default).