Skip to content
Skills Library
DevOps & cloud · Automation

fieldflow-cli

/fieldflow-cli

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.

Repository
fieldflow ↗
Licence
MIT
Last repository change
20.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

  1. Qualify The Command
  2. Inspect First
  3. Pick Minimal Fields
  4. Run The Reduced Command
  5. JSON Output Rules
  6. Gcloud Example
Original SKILL.md headings · 107 lines, 412 words
SKILL.md preview
---
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
```
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named fieldflow-cli.

Database snapshot: 13.11.2026 · package version 5c52aac12b98 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100using-cloud-cli
    Cloud CLI patterns for GCP and AWS. Use when running bq queries, gcloud commands, aws commands, or making decisions about cloud services. Covers BigQuery cost optimization and operational best practices.
  • 100gcloud
    为跨 Google Cloud Platform (GCP) 服务和基础设施的 gcloud CLI 操作提供安全关键的校验、防护措施和数据精简。 在规划、生成、构造、提议、描述或执行任何 gcloud CLI 命令时使用——包括回答关于 gcloud 语法或标志格式的问题时。 不要在编写 Google Cloud 客户端库代码或原始 REST/gRPC API 请求时使用。
  • 100k8s-cli
    kubectl-mcp-server CLI commands for tool discovery, direct invocation, and diagnostics. Use when exploring available tools, calling tools from command line, or checking server health.
  • 100safe-sre-investigator
    🐉 Sets up and uses read-only Service Accounts for GCP and Kubernetes investigations using the principle of least privilege, and provides risk assessments for suggested commands. Use when asked to investigate GCP/GKE resources or suggest gcloud/kubectl commands.
  • 100gcloud
    Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services and infrastructure. Use when planning, generating, constructing, proposing, describing, or executing any gcloud CLI commands - including when…
  • 100gcloud
    Expert Google Cloud CLI guidance. Use when the task involves gcloud commands or the Google Cloud SDK — installing or updating the CLI and components (bq, gsutil, kubectl, gke-gcloud-auth-plugin, alpha/beta), gcloud init, authentication issues (gcloud auth login vs…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.