Agent skill

Fieldflow CLI

by guillaumegay13 in guillaumegay13/fieldflow

Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context.

MITAuto-check passedAI & LLM Engineering

Install Fieldflow CLI

skills CLI
$ npx skills add guillaumegay13/fieldflow --skill fieldflow-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install guillaumegay13/fieldflow fieldflow-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/guillaumegay13/fieldflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fieldflow-cli .claude/skills/fieldflow-cli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fieldflow-cli
GitHub stars
110
Token cost
~872 tokens
SKILL.md length
295 words
Files
2
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context.

  • Read-only external CLI tasks likely to return large structured output
  • SKILL.md covers Qualify The Command, Inspect First, Pick Minimal Fields and Run The Reduced Command, plus 2 more sections
  • Calls gcloud and git
  • Especially logs

What it does

Fieldflow CLI is an agent skill from guillaumegay13/fieldflow. Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context. Trigger for read-only external CLI tasks likely to return large structured output, especially logs, list, describe, get, read, query, search, metrics, or status commands from tools like gcloud, gh, kubectl, aws, or similar CLIs that can emit JSON. Prefer fieldflow-cli inspect first, then rerun with explicit --field selectors. Do not use for tiny local commands, text-only commands, or mutating commands unless explicitly asked.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in AI & LLM Engineering, covering Container orchestration and Structured output and tool calling. It works with Google Cloud, Amazon Web Services, Kubernetes and Model Context Protocol. The licence is MIT.

When your agent uses it

  • Read-only external CLI tasks likely to return large structured output
  • Especially logs
  • Status commands from tools like gcloud
  • Similar CLIs that can emit JSON

Example prompts

  • “/fieldflow-cli”

What it can do on your machine

Read from SKILL.md and the folder at commit dde727f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gcloud
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gcloud and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fieldflow CLI loads about 872 tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 295 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~135
When it runs · the whole SKILL.md, loaded when a task matches
~872

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from guillaumegay13/fieldflow at commit dde727f, republished under its MIT licence (© guillaumegay13). 295 words, ~872 tokens.

Download SKILL.mdSave it as .claude/skills/fieldflow-cli/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
fieldflow-cli
description
Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context. Trigger for read-only external CLI tasks likely to return large structured output, especially logs, list, describe, get, read, query, search, metrics, or status commands from tools like gcloud, gh, kubectl, aws, or similar CLIs that can emit JSON. Prefer `fieldflow-cli inspect` first, then rerun with explicit `--field` selectors. Do not use for tiny local commands, text-only commands, or mutating commands unless explicitly asked.

FieldFlow CLI

Use this skill to keep large JSON CLI output out of model context.

Qualify The Command

Use fieldflow-cli only when all of these are true:

  • The command is read-only.
  • The command is external or service-facing, not a tiny local shell command.
  • The command can emit JSON on stdout.
  • The expected output is likely large enough that raw output would pollute context.

Do not use this skill for commands like pwd, date, ls, git status, rg, or any mutating command such as deploy, apply, delete, or create.

Inspect First

Run fieldflow-cli inspect before choosing selectors unless you already have a manifest for the exact same wrapped command.

bash
fieldflow-cli inspect --sample-items 100 -- <wrapped command>

The inspect step writes a compact field catalog under .fieldflow/inspect/ and prints the manifest to stdout. Treat that manifest as the source of truth for valid selectors.

The manifest is deterministic and intentionally small:

  • path
  • types

It does not store raw command output.

Pick Minimal Fields

Choose the smallest field set that answers the user’s question.

Prefer fields like:

  • timestamps
  • severity or status
  • identifiers or names
  • URLs
  • concise message fields
  • latency, count, or state fields

Avoid broad selectors such as [] or whole nested objects unless the task truly needs them.

Run The Reduced Command

After choosing selectors, rerun the command through fieldflow-cli.

bash
fieldflow-cli \
  --field "[].timestamp" \
  --field "[].severity" \
  --field "[].jsonPayload.message" \
  -- \
  <wrapped command>

If the result is too narrow, broaden the selectors and rerun the reduced call. Do not fall back to raw output unless the user explicitly asks for it.

JSON Output Rules

Prefer the CLI’s native JSON mode:

  • gcloud: --format=json
  • kubectl: -o json
  • gh: --json ...
  • aws: JSON is already standard, or use --output json when needed

If the command cannot emit JSON, do not use this skill.

Gcloud Example

For noisy Cloud Run request or error logs:

bash
fieldflow-cli inspect --sample-items 100 -- \
  gcloud logging read \
    'resource.type="cloud_run_revision" AND resource.labels.service_name="program-api-service" AND severity>=ERROR' \
    --project=train-3328b \
    --freshness=24h \
    --limit=2000 \
    --format=json

Then reduce to the smallest useful fields, for example:

bash
fieldflow-cli \
  --field "[].timestamp" \
  --field "[].severity" \
  --field "[].httpRequest.requestMethod" \
  --field "[].httpRequest.requestUrl" \
  --field "[].httpRequest.status" \
  --field "[].httpRequest.latency" \
  -- \
  gcloud logging read \
    'resource.type="cloud_run_revision" AND resource.labels.service_name="program-api-service" AND severity>=ERROR' \
    --project=train-3328b \
    --freshness=24h \
    --limit=2000 \
    --format=json

© guillaumegay13, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/fieldflow-cli of guillaumegay13/fieldflow.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit dde727f

Compare with similar skills

Fieldflow CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fieldflow CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fieldflow CLI this skillguillaumegay13/fieldflow110—~872Automated safety check: PassMIT
Provider Bug Reviewmondoohq/mql411—~2.9kAutomated safety check: PassCustom licence
Kcli Cluster Deploymentkarmab/kcli653—~1.5kAutomated safety check: PassApache-2.0
Logfire Infrastructurepydantic/skills140—~1.8kAutomated safety check: PassMIT
Eks Best Practicesaws-samples/appmod-blueprints113—~5kAutomated safety check: PassMIT-0
Extend Discovery Typerunwhen-contrib/runwhen-local163—~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

    411 GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Guides deployment and management of Kubernetes clusters with kcli.

    653 GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Logfire Infrastructure

    pydantic/skills

    Official

    Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.

    140 GitHub stars~1.8k tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed
  • Eks Best Practices

    aws-samples/appmod-blueprints

    Official

    Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.

    113 GitHub stars~5k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Extend Discovery Type

    runwhen-contrib/runwhen-local

    Add or enrich a resource type in an existing RunWhen Local discovery indexer (Azure azureapi, GCP gcpapi, AWS, or Kubernetes).

    163 GitHub stars~1.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Kcli

    karmab/kcli

    Comprehensive guide for kcli usage. An agent skill from karmab/kcli.

    653 GitHub stars~2.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: warnings

Questions about Fieldflow CLI

What does Fieldflow CLI do?

Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context. Fieldflow CLI is an agent skill from guillaumegay13/fieldflow. Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context.

When should I use Fieldflow CLI?

Fieldflow CLI fits situations like: read-only external CLI tasks likely to return large structured output; especially logs; status commands from tools like gcloud; similar CLIs that can emit JSON.

How do I install Fieldflow CLI in Claude Code?

Run `npx skills add guillaumegay13/fieldflow --skill fieldflow-cli -a claude-code`. Or copy the skill folder (.agents/skills/fieldflow-cli in guillaumegay13/fieldflow) into .claude/skills/fieldflow-cli in your project. Claude Code loads it when a task matches its description.

How do I install Fieldflow CLI in Codex?

Run `npx skills add guillaumegay13/fieldflow --skill fieldflow-cli -a codex`. Or copy the skill folder (.agents/skills/fieldflow-cli in guillaumegay13/fieldflow) into .agents/skills/fieldflow-cli in your project. Codex loads it when a task matches its description.

Can I use Fieldflow CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add guillaumegay13/fieldflow --skill fieldflow-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fieldflow-cli, .gemini/skills/fieldflow-cli, .github/skills/fieldflow-cli and .opencode/skills/fieldflow-cli in your project.

What does Fieldflow CLI need to run?

Going by SKILL.md and its folder, Fieldflow CLI needs the command-line tools its instructions call (gcloud and git).

Does Fieldflow CLI access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Fieldflow CLI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fieldflow CLI use?

Fieldflow CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fieldflow CLI use?

About 872 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fieldflow CLI?

Skills that share tags, products or a category with Fieldflow CLI: Provider Bug Review (mondoohq/mql, 411 stars), Kcli Cluster Deployment (karmab/kcli, 653 stars), Logfire Infrastructure (pydantic/skills, 140 stars) and Eks Best Practices (aws-samples/appmod-blueprints, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fieldflow CLI?

guillaumegay13 (a GitHub user) maintains it in guillaumegay13/fieldflow, which has 110 GitHub stars. The repository was last updated on July 22, 2026.

Source: guillaumegay13/fieldflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.