fft setup

Engineering Community

Skill notes

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.sh from 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 the NANO_CORE_ALLOW_HOST_RUNTIME=1 env override (set explicitly, never default).

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
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.

Author source file SKILL.md

# 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).

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.