fft-coder-ops

Engineering Community

Repo stars 0
Author repo nano-core

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Operate FFT_nano coding delegation flows safely using /coder and /coder-plan, preserving main-chat-only policy, request-id track…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to use this skill”, “When not to use this skill”, “Guardrails”, “Delegation Triggers”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name fft-coder-ops directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to use this skill / When not to use this skill / Guardrails” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @0-CYBERDYNE-SYSTEMS-0 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview fft-coder-ops.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# FFT Coder Ops

Use this skill when handling coding delegation operations in FFT_nano.

## When to use this skill

- Use for `/coder` and `/coder-plan` delegation workflows.
- Use when enforcing main/admin chat boundaries for coding execution.
- Use when tracking delegated run IDs and progress-stream behavior.

## When not to use this skill

- Do not use for non-coding tasks or normal chat replies.
- Do not use when no explicit delegation trigger is present.
- Do not use in non-main chats for delegated execution.

## Guardrails

- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Never bypass main-chat-only coder delegation safety rules.
- Do not add automatic delegation; delegation remains explicit trigger-based.

## Delegation Triggers

Explicit execute:

- `/coder <task>`
- `use coding agent`
- `use your coding agent skill`

Explicit plan-only:

- `/coder-plan <task>`

Natural-language coding requests without explicit trigger must not auto-delegate.

## Chat Safety Rules

- Delegation is only available in main/admin chat.
- Non-main chats may request coding help, but must be handled directly or rejected for delegation.
- Scheduled tasks must not trigger coder delegation.

## Runtime Expectations

- Execute mode delegates once and returns delegated outcome.
- Plan mode returns implementation/test plan without direct edits in outer orchestrator turn.
- Delegation run IDs are generated (`coder-<timestamp>-<suffix>`) and surfaced in progress messages.
- Progress streaming should avoid final duplicate full-message sends.

## Operator Commands

Main Telegram chat commands:

- `/coder <task>`
- `/coder-plan <task>`

Alias phrases in main chat:

- `use coding agent`
- `use your coding agent skill`

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> When to use this skill → When not to use this skill → Guardrails → Delegation Triggers → Chat Safety Rules → Runtime Expectations
terms    -> Use this skill when handling coding delegation operations in FFTnano. · - Use for /coder and /coder-plan delegation workflows. · - Do not use for non-coding tasks or normal chat replies. · - Never run destructive git commands unless explicitly requested. · Natural-language coding requests without explicit trigger must not auto-delegate. · - Delegation is only available in main/admin chat. · - Execute mode delegates once and returns delegated outcome. · - Non-main /coder is rejected with safety message.
files/cmd -> /coder · /coder-plan · /coder <task> · use coding agent · use your coding agent skill · /coder-plan <task> · coder-<timestamp>-<suffix>
body sha256 -> 8c2b6f38b837

fft-coder-ops

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

FFT Coder Ops

When to use this skill

When not to use this skill

Guardrails

Delegation Triggers

Chat Safety Rules

Runtime Expectations

Operator Commands

Validation Checklist

Discussion