Fieldops engineering
Dual-runtime Agent Skills for Claude Code, Codex GPT, CC Switch, and authorized CTF workflows.
npx -y skills add download4you/n2-fieldops --skill fieldops-engineeringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Diagnoses, implements, and verifies non-trivial or risk-sensitive changes in an existing repository while preserving the user's uncommitted work, following repository instructions (AGENTS.md or CLAUDE.md), keeping edits within authorized scope, and handing off with runtime evidence. Use when the user asks to fix a bug, add or change a feature, refactor, migrate, edit configuration, chase down a regression, or make a change safely amid overlapping edits or worktrees where verification and change control matter. Not for isolated code snippets or simple explanations; for diagnosis-only requests, prove and explain the cause without fixing unless asked.
SKILL.md
1.4 KB, 138 tokens by cl100k_base, as published. Nobody here has run it
Engineering FieldOps
- Classify authorization with
references/authorization.md. - Read applicable repository instructions and inspect the worktree.
- Establish current behavior with runtime evidence or a focused reproduction.
- Identify the smallest coherent change.
- Preserve unrelated edits and use reviewable patches.
- Verify proportionally with
references/verification.md. - Review the final diff for scope expansion.
- Report outcome, files, verification, and unresolved risk.
Read references/safe-editing.md before Git or overlapping-file work. Prefer rg and focused reads. Never revert user changes, amend commits, or use destructive Git operations without explicit authority.
Gives 0 of the 12 instructions most memory context skills give in 138 tokens
Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06
- inform the user when setup is completein 21 of 674, across 6 files
- confirm the draft with the user before writingin 21 of 674, across 6 files
- update the agent skills block in place if it existsin 21 of 674, across 6 files
- present findings to the userin 20 of 674, across 5 files
- write the three docs files from seed templatesin 20 of 674, across 5 files
- ask the user about each decision one at a timein 19 of 674, across 4 files
- edit CLAUDE.md if it existsin 18 of 674, across 3 files
- explore current repo statein 18 of 674, across 3 files
- do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
- back up the original file before overwritingin 16 of 674, across 8 files
- keep the memory index under 200 linesin 15 of 674
- Provide actionable steps and verificationin 13 of 674, across 2 files
Said here and by no other author read
- classify authorization
- inspect the worktree
- establish current behavior
- identify the smallest coherent change
- verify changes proportionally
- review the final diff
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.