New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Nifi Flow Layout

by Kilo-Org in Kilo-Org/kilo-marketplace

A skill your agent uses when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts.

MITAuto-check passedTesting & QA

Install Nifi Flow Layout

skills CLI
$ npx skills add Kilo-Org/kilo-marketplace --skill nifi-flow-layout -a claude-code

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

GitHub CLI
$ gh skill install Kilo-Org/kilo-marketplace nifi-flow-layout --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/Kilo-Org/kilo-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nifi-flow-layout .claude/skills/nifi-flow-layout && 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
nifi-flow-layout
GitHub stars
190
Token cost
~1.5k tokens
SKILL.md length
648 words
Files
5 (incl. scripts, references)
Skills in repo
86
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts.

  • Works in 3 steps: Inspect first → Apply the house style → Verify visually
  • Arranging Apache NiFi processors
  • SKILL.md covers Workflow, Scripts, Typical commands and Non-negotiable visual rules…, plus 2 more sections
  • Runs Python and JavaScript scripts from its folder; calls python3

What it does

Nifi Flow Layout is an agent skill from Kilo-Org/kilo-marketplace. Use when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/layout-rules.md` and `scripts/nifi_layout.py`).

It sits in Testing & QA. It works with Playwright. The repository describes itself as: Kilo Marketplace - A curated collection of Skills, MCP Servers, and Modes for enhancing AI agent capabilities across the Kilo ecosystem—including Kilo Code (VS Code extension)… The licence is MIT.

When your agent uses it

  • Arranging Apache NiFi processors
  • Crossing connections
  • Dense fan-in/fan-out
  • Reusable readable canvas layouts

Example prompts

  • “/nifi-flow-layout”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Inspect first
  2. Apply the house style
  3. Verify visually

What it can do on your machine

Read from SKILL.md and the folder at commit ff51758. 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

    Ships 2 files in scripts/ (Python and JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

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

  • Network

    No URLs in SKILL.md.

    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

Nifi Flow Layout loads about 1.5k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 648 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.9k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from Kilo-Org/kilo-marketplace at commit ff51758, republished under its MIT licence (© Kilo-Org). 648 words, ~1,481 tokens.

Download SKILL.mdSave it as .claude/skills/nifi-flow-layout/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
nifi-flow-layout
description
Use when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts.
metadata.category
data

NiFi Flow Layout

Use this universal skill when any Apache NiFi flow must be readable a year later: clear names, useful comments, compact vertical flow, and connections that do not cross blocks. The skill has no environment-specific defaults: pass the NiFi URL, credentials/certificates, and target process group explicitly.

Workflow

  1. Inspect first

    • Read the target process group through NiFi REST.
    • Save a JSON snapshot before changing anything.
    • Run audit/dry-run before apply.

  2. Apply the house style

    • Main route goes top-to-bottom.
    • Input/source nodes go to the top boundary; output/terminal sinks go to the bottom boundary.
    • Errors/logs/fallback/notification branches go to a side lane.
    • Connections are orthogonal: vertical/horizontal, no diagonals.
    • Connection names stay empty. Connections do not support comments in NiFi.
    • Every commentable object gets a useful human comment: processor, process group, input port, output port.
    • Names use hierarchical numbering: 10, 20, 30, then 30.10, 30.20, then 30.20.10. Never use .00.
    • Move processors/ports before drawing long detours. A cleaner node position is better than a giant route rectangle.

  3. Verify visually

    • Use Playwright when available to capture real DOM bounding boxes and a screenshot.
    • Treat route/label overlap with processors, process groups, ports, or queued boxes as a defect.

Scripts

  • scripts/nifi_layout.py — REST audit, dry-run, apply, geometry tests.
  • scripts/nifi_visual_check.cjs — Playwright screenshot and DOM bounding-box capture.
  • references/layout-rules.md — detailed rules and routing decisions.

Typical commands

bash
python3 scripts/nifi_layout.py \
  --base-url https://nifi.example.com/nifi-api \
  --group-id <process-group-id> \
  --cert /path/client.crt --key /path/client.key \
  --mode audit --recursive
bash
python3 scripts/nifi_layout.py \
  --base-url https://nifi.example.com/nifi-api \
  --group-id <process-group-id> \
  --cert /path/client.crt --key /path/client.key \
  --mode dry-run --recursive --backup-dir ./nifi-backups
bash
python3 scripts/nifi_layout.py \
  --base-url https://nifi.example.com/nifi-api \
  --group-id <process-group-id> \
  --cert /path/client.crt --key /path/client.key \
  --mode apply --recursive --backup-dir ./nifi-backups

Non-negotiable visual rules from real reviews

  • Verify with Playwright screenshots after changes; REST geometry is not enough.
  • Use boundary-aware layers: sources at top, business processors in middle, terminal outputs at bottom.
  • Before adding bends, try moving the source/destination into a cleaner layer or closer side lane.
  • Do not leave a huge empty left/right canvas area while another side is overloaded with route loops.
  • For dense fan-in, evaluate all useful target sides. Do not force every branch into one side or one shared point.
  • Dense fan-in must stay local and comb-shaped. Do not move a sink far away just to make route scoring pass.
  • If a lower source crosses the central bus/labels when entering from the left, try right-side entry, but only after checking the full candidate route for component and label blockers.
  • Treat connection labels as real obstacles. Lines must not pass through Name/Queued boxes, even if they do not touch processors.
  • Side handler returns should avoid queue labels between main-lane processors. Use a clear side/bottom lane instead of a short route that hides under labels.
  • Side handler → output port should not add tiny doglegs when the output centerline is clear; prefer the compact side route.
  • Always inspect screenshots for the whole affected area, not only one cropped defect. If the flow is larger than a viewport, pan/scroll and capture more screenshots.
Show full SKILL.md (208 more words)Show less

Safety rules

  • Do not print secrets or certificate passphrases.
  • Do not edit processor business properties unless the user explicitly asked.
  • Default to audit/dry-run; use apply only when implementation is requested.
  • Preserve revisions and current processor state; only update names, comments, positions, connection bends, labelIndex, and empty connection names.
  • Before apply, always write a backup flow JSON using --backup-dir.

Review hardening additions

  • scripts/nifi_layout.py supports --single-group, --group-order top-down, --report-dir, --screenshots-dir, --visual-gate, and PKCS#12 auth via --p12.
  • Apply mode is state-preserving by default: processor/port metadata updates do not stop running components; connection updates first try without stopping and only retry by stopping the two endpoint components when the connection queue is empty.
  • scripts/nifi_visual_check.cjs supports --tile-grid CxR and --tile-dir for large-canvas evidence.
  • Dense fan-in, same-column side chains, side-column handler returns, hard label packing, 12px visual label/component clearance, and 32px visual line spacing are handled to prevent merged wires, processor overlaps, queued-label overlaps, and near-touching lines.
  • Treat visual X/T line crossings as hard defects; use wider bus lanes instead of ambiguous intersections.
  • Non-adjacent segments of the same connection must also keep wide spacing; self-overlapping U-turns are defects.
  • Reports include topology_blockers when a clean visual layout likely requires a graph decision, such as adding a funnel, collector processor, split sink, or separate process group.

© Kilo-Org, 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 4 other files (scripts, references) in skills/nifi-flow-layout of Kilo-Org/kilo-marketplace.

  • SKILL.md
  • LICENSE
  • references/layout-rules.md
  • scripts/nifi_layout.py
  • scripts/nifi_visual_check.cjs

Open the folder on GitHubat commit ff51758

Compare with similar skills

Nifi Flow Layout 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.

Nifi Flow Layout compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nifi Flow Layout this skillKilo-Org/kilo-marketplace190—~1.5kAutomated safety check: PassMIT
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Playwright CLIsanity-io/sanity6.4k18 repos~1.9kAutomated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.4k23 repos~2.8kAutomated safety check: PassMIT
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Playwright CLI

    sanity-io/sanity

    Official

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    6.4k GitHub starsUsed in 18 repos~1.9k tokens
    Testing & QAAuto-check passed

  • Write and Verify Playwright Tests

    appsmithorg/appsmith

    Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check: notes

  • playwright-cli Browser Automation

    github/gh-aw

    Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.4k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed

  • Cucumber and Playwright E2E Tests

    langgenius/dify

    Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed

  • Verify Openhands

    OpenHands/OpenHands

    This skill should be used to "verify OpenHands features", "test the Canvas UI like a user", "drive Agent Canvas", "check a UI change in the real app", "create or update the feature map", "run the…

    90k GitHub stars~3.4k tokensUpdated today
    Testing & QAAuto-check passed

More from Kilo-Org/kilo-marketplace

All 86 skills in this repo

  • AzureML Project Scaffolding

    Kilo-Org/kilo-marketplace

    Sets up and maintains AzureML-ready Python projects as uv workspaces with devcontainers, a Makefile and job YAML, so local runs match cloud jobs and experiments stay reproducible.

    190 GitHub stars~3.1k tokensUpdated 10 days ago
    Auto-check: notes

  • Jupyter Notebook Builder

    Kilo-Org/kilo-marketplace

    Creates, inspects, edits and runs Jupyter notebooks, scaffolding experiment or tutorial notebooks from templates and preferring a Jupyter MCP server over raw JSON edits.

    190 GitHub stars~1.3k tokensUpdated 10 days ago
    Auto-check passed

  • Tableau Dashboard Creator

    Kilo-Org/kilo-marketplace

    Takes a plain-language dashboard request through brand setup, data exploration, planning, an interactive HTML mock and a Tableau implementation spec.

    190 GitHub stars~3.8k tokensUpdated 10 days ago
    Auto-check: notes

  • Elasticsearch File Ingest

    Kilo-Org/kilo-marketplace

    Ingest and transform data files (CSV/JSON/Parquet/Arrow IPC) into Elasticsearch with stream processing and custom transforms.

    190 GitHub stars~2.8k tokensUpdated 10 days ago
    Auto-check passed

  • Splunk Ingest Processor Setup

    Kilo-Org/kilo-marketplace

    Render Cisco Data Fabric ingest-time routing workflows and Splunk Cloud Platform Ingest Processor setup plans with SPL2 pipelines, source types, destinations, lifecycle handoffs, queue and…

    190 GitHub stars~1.2k tokensUpdated 10 days ago
    Auto-check passed

  • Databricks Jobs

    Kilo-Org/kilo-marketplace

    Develop and deploy Lakeflow Jobs on Databricks via DABs, Python SDK, or the CLI.

    190 GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed

Works with

Categories

Questions about Nifi Flow Layout

What does Nifi Flow Layout do?

A skill your agent uses when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts. Nifi Flow Layout is an agent skill from Kilo-Org/kilo-marketplace. Use when arranging Apache NiFi processors, process groups, ports, comments, numbering, crossing connections, dense fan-in/fan-out, or reusable readable canvas layouts.

When should I use Nifi Flow Layout?

Nifi Flow Layout fits situations like: arranging Apache NiFi processors; crossing connections; dense fan-in/fan-out; reusable readable canvas layouts.

How do I install Nifi Flow Layout in Claude Code?

Run `npx skills add Kilo-Org/kilo-marketplace --skill nifi-flow-layout -a claude-code`. Or copy the skill folder (skills/nifi-flow-layout in Kilo-Org/kilo-marketplace) into .claude/skills/nifi-flow-layout in your project. Claude Code loads it when a task matches its description.

How do I install Nifi Flow Layout in Codex?

Run `npx skills add Kilo-Org/kilo-marketplace --skill nifi-flow-layout -a codex`. Or copy the skill folder (skills/nifi-flow-layout in Kilo-Org/kilo-marketplace) into .agents/skills/nifi-flow-layout in your project. Codex loads it when a task matches its description.

Can I use Nifi Flow Layout 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 Kilo-Org/kilo-marketplace --skill nifi-flow-layout -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nifi-flow-layout, .gemini/skills/nifi-flow-layout, .github/skills/nifi-flow-layout and .opencode/skills/nifi-flow-layout in your project.

What does Nifi Flow Layout need to run?

Going by SKILL.md and its folder, Nifi Flow Layout needs Python and JavaScript for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Nifi Flow Layout access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nifi Flow Layout 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Nifi Flow Layout use?

Nifi Flow Layout is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nifi Flow Layout use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Nifi Flow Layout?

Skills that share tags, products or a category with Nifi Flow Layout: Web Application Testing (anthropics/skills, 180k stars), Playwright CLI (sanity-io/sanity, 6.4k stars), Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars) and playwright-cli Browser Automation (github/gh-aw, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nifi Flow Layout?

Kilo-Org (a GitHub organization) maintains it in Kilo-Org/kilo-marketplace, which has 190 GitHub stars. The repository holds 86 skills in this directory. The repository was last updated on September 28, 2026.

Source: Kilo-Org/kilo-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.