Agent skill

Skill Preflight

Deliver a pre-flight duplicate check before creating new skills or agents.

Install Skill Preflight

skills CLI

$ npx skills add flonat/flonat-research --skill skill-preflight -a claude-code

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

GitHub CLI

$ gh skill install flonat/flonat-research skill-preflight --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/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-preflight .claude/skills/skill-preflight && 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/

Paste into Claude Code

Install the "skill-preflight" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/skill-preflight into .claude/skills/skill-preflight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-preflight", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/skill-preflight

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add flonat/flonat-research --skill skill-preflight -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research skill-preflight --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-preflight .agents/skills/skill-preflight && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "skill-preflight" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/skill-preflight into .agents/skills/skill-preflight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-preflight", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill skill-preflight -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research skill-preflight --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-preflight .cursor/skills/skill-preflight && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "skill-preflight" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/skill-preflight into .cursor/skills/skill-preflight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-preflight", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/skill-preflight

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flonat/flonat-research --skill skill-preflight -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research skill-preflight --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-preflight .gemini/skills/skill-preflight && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "skill-preflight" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/skill-preflight into .gemini/skills/skill-preflight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-preflight", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install flonat/flonat-research skill-preflight

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add flonat/flonat-research --skill skill-preflight -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-preflight .github/skills/skill-preflight && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "skill-preflight" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/skill-preflight into .github/skills/skill-preflight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-preflight", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill skill-preflight -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research skill-preflight --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-preflight .opencode/skills/skill-preflight && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "skill-preflight" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/skill-preflight into .opencode/skills/skill-preflight/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-preflight", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: skill-preflight
GitHub stars: 145
Token cost: ~2.1k tokens
SKILL.md length: 825 words
Files: 1
Skills in repo: 83
Repo updated: Sep 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Deliver a pre-flight duplicate check before creating new skills or agents.

Works in 5 steps: Identify the Proposal → Search Existing Artifacts → Analyse Overlap → …
The user requests a pre-flight duplicate check before creating new skills
SKILL.md covers When to Use, Process, Output Format and Recommendation Details, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Skill Preflight is an agent skill from flonat/flonat-research. Deliver a pre-flight duplicate check before creating new skills or agents. Use when the user requests a pre-flight duplicate check before creating new skills or agents.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

The user requests a pre-flight duplicate check before creating new skills

Example prompts

“/skill-preflight”

Requirements

Docker
Pre-approved tools (allowed-tools): Read, Glob, Grep, AskUserQuestion

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Identify the Proposal
Search Existing Artifacts
Analyse Overlap
Generate Recommendation
Present and Confirm

What it can do on your machine

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

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Glob
- Grep
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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

Skill Preflight loads about 2.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 825 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: ~2.1k

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 flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 825 words, ~2,147 tokens.

Download SKILL.mdSave it as .claude/skills/skill-preflight/SKILL.md (or your agent's skills folder).

name: skill-preflight
description: Deliver a pre-flight duplicate check before creating new skills or agents. Use when the user requests a pre-flight duplicate check before creating new skills or agents.
allowed-tools: Read, Glob, Grep, AskUserQuestion

Creation Guard: Pre-Flight Duplicate Check

Prevent duplicate functionality by analysing existing skills, agents, and rules before creating new ones. Intercepts creation intent, searches for overlap, and recommends one of 5 actions.

When to Use

Invoke before creating ANY new:

Skill (skills/*/SKILL.md)
Agent (.claude/agents/*.md)
Rule (rules/*.md)

Trigger phrases:

"Create a skill for..."
"I want a new skill that..."
"Let's add an agent for..."
"We need a rule for..." / "add a rule that..."
Any intent to create new automation/tooling

Rules need this most, not least. A duplicate skill is visible — it shows up in the catalogue and the slash menu. A duplicate rule is invisible: both copies load silently as system instructions, and the first sign of trouble is two subtly different versions of the same policy competing. Rules are also break-the-glass infrastructure, so an unnecessary one is a standing cost on every session. Check for an existing rule to amend before writing a new one — amendment is the usual correct outcome for rules, where PROCEED is the usual outcome for skills.

Process

Step 1: Identify the Proposal

Extract from the request:

Name: Proposed name (kebab-case)
Type: skill | agent | rule
Purpose: What it does (one sentence)
Key Functions: 3-5 main capabilities
Keywords: Searchable terms related to functionality

Step 2: Search Existing Artifacts

Run these searches in parallel:

Read skills/shared/skill-index.md — scan the categorised table for potential duplicates by name and purpose
Keyword search — grep skills, agents, and rules for each keyword:

Grep for each keyword across:
  - skills/*/SKILL.md (frontmatter + body)
  - .claude/agents/*.md (frontmatter + body)
  - rules/*.md (frontmatter + body)

Agent scan — read frontmatter of each agent to check purpose overlap:

Glob: .claude/agents/*.md
Read first 20 lines of each match

Rule scan — list every rule and read its Principle:

Glob: rules/*.md
Read the frontmatter + "## Principle" section of each candidate

A rule's filename often understates its reach: the policy you want may live inside a broader rule under a different name. Check docs/components/rules.md for the full table, and read the Principle rather than matching on the title — bibliography-routing.md owns paper-lookup routing, which its name does not advertise. Also check the paths: frontmatter: a rule that exists but is path-scoped away from where you need it is a scoping fix, not a new rule.

Step 3: Analyse Overlap

For each potentially related artifact, assess:

Criterion	Question
Functional overlap	Does it do the same thing? (0-100%)
Naming confusion	Could names be confused?
Extension potential	Could the proposal extend this instead?
Composition	Could existing artifacts compose to achieve this?

Step 4: Generate Recommendation

Based on analysis, recommend ONE of:

Recommendation	Criteria	Action
PROCEED	<20% overlap, genuinely new capability	Create new artifact
EXTEND	50%+ overlap with single existing artifact	Modify existing instead
COMPOSE	Multiple artifacts cover 80%+ combined	Create thin wrapper or document workflow
ITERATE	20-50% overlap, proposal needs refinement	Refine proposal to differentiate
BLOCK	Would create problematic duplication	Do not create

Step 5: Present and Confirm

Display the analysis and wait for explicit user approval before proceeding.

Output Format

════════════════════════════════════════════════════════════════
CREATION GUARD ANALYSIS
════════════════════════════════════════════════════════════════

PROPOSAL:
  Type: [skill|agent]
  Name: [proposed-name]
  Purpose: [one sentence]

EXISTING ARTIFACTS ANALYSED: [count]

RELATED ARTIFACTS FOUND:

1. [artifact-name] ([type])
   Purpose: [what it does]
   Overlap: [X]% - [explanation]

2. [artifact-name] ([type])
   Purpose: [what it does]
   Overlap: [X]% - [explanation]

RECOMMENDATION: [PROCEED|EXTEND|COMPOSE|ITERATE|BLOCK]

RATIONALE:
[2-3 sentences explaining the recommendation]

SUGGESTED ACTION:
[Specific next step based on recommendation]

════════════════════════════════════════════════════════════════

Recommendation Details

PROCEED

Artifact is genuinely new
No significant overlap found
Clear differentiation from existing tools
Go ahead and create

EXTEND

Present extension proposal:

Instead of creating [new-name], extend [existing-name]:

Current capabilities:
- [existing feature 1]
- [existing feature 2]

Proposed additions:
- [new feature 1]
- [new feature 2]

COMPOSE

Present composition approach:

The proposed functionality can be achieved by combining:

1. [artifact-1] — handles [aspect]
2. [artifact-2] — handles [aspect]

Options:
A) Document this workflow (no new code)
B) Create thin orchestration skill
C) Add to existing skill's integration section

ITERATE

Present refinement questions:

Overlap detected with [existing-artifact].

Differentiation needed:
1. [question about scope]
2. [question about use case]
3. [question about implementation]

Please clarify to proceed.

BLOCK

Explain why creation should not proceed:

BLOCKED: Would create problematic duplication.

Existing artifact: [name]
- Already does: [capabilities]
- Your request: [same capabilities]

Alternatives:
1. Use existing: /[skill-name]
2. If missing features, extend the existing artifact
3. If different use case, explain how this differs

Show full SKILL.md (328 more words)Show less

Post-Match Action Table

When overlap IS found, use this table to decide the specific action:

Situation	Action
Nothing related found	Create new artifact
Same trigger + same fix as existing	Update existing (bump version, improve docs)
Same trigger, different root cause	Create new + add cross-links in both
Partial overlap (same domain, different trigger)	Add variant subsection to existing
Same domain, different problem	Create new + add "See also" references
Existing is stale or wrong	Mark deprecated + create replacement

This complements the PROCEED/EXTEND/COMPOSE/ITERATE/BLOCK recommendation above. The recommendation decides whether to create; this table decides how to handle the relationship with existing artifacts.

Self-Check Questions

Before creating ANY new artifact, ask:

Does something similar already exist?
Could this be added to an existing artifact?
Would a user know to look for this vs the existing one?
Am I creating this because it's needed or because it's easier than finding what exists?

Naming Convention Enforcement

When creating a new skill, always name the definition file SKILL.md (uppercase). Never skill.md, Skill.md, or any other casing.

The MCP server's skill discovery scans for SKILL.md explicitly
Documentation generators and system-audit use find -name 'SKILL.md'
On case-insensitive filesystems (macOS APFS), lowercase files appear to work locally but fail in case-sensitive contexts (Linux CI, Docker, MCP server pattern matching)

Check before writing: If the target directory already contains a skill.md (lowercase), rename it to SKILL.md first.

Anti-Patterns

Anti-Pattern	Problem	Instead
Skip the check	"It's obviously new" — famous last words	Always run the analysis
Name-only matching	Names differ but functions overlap	Search by purpose and keywords
Create then merge	Merge debt accumulates fast	Check first, create once
Over-splitting	Two skills that always run together	Consider a single skill with phases
Lowercase `skill.md`	Invisible to MCP server, audit tools, and case-sensitive systems	Always use `SKILL.md` (uppercase)

Integration

This skill is invoked by skill-extract in Phase 2 to replace the old subset/partial/no-overlap check. When called from skill-extract, return the recommendation label (PROCEED/EXTEND/COMPOSE/ITERATE/BLOCK) so skill-extract can branch accordingly.

Files

Just SKILL.md in skills/skill-preflight of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Skill Preflight 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.

Skill Preflight compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Skill Preflight this skillflonat/flonat-research	145	—	~2.1k	Automated safety check: Pass	MIT	9 days ago
MCP Server Builderanthropics/skills	180k	64 repos	~2.3k	Automated safety check: Pass	Apache-2.0	2 days ago
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	38k	11 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today
Using Superpowersfarm-fe/farm	5.6k	35 repos	~1.4k	Automated safety check: Pass	MIT	16 days ago
Executing Plans Inlineobra/superpowers	296k	2 repos	~5.1k	Automated safety check: Pass	MIT	today
Claude Code Agent Developmentanthropics/claude-plugins-official	38k	8 repos	~2.8k	Automated safety check: Pass	Apache-2.0	today

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 64 repos~2.3k tokens
Agent WorkflowsAuto-check passed
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
38k GitHub starsUsed in 11 repos~4.1k tokens
Agent WorkflowsAuto-check: notes
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
5.6k GitHub starsUsed in 35 repos~1.4k tokens
Agent WorkflowsAuto-check passed
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
296k GitHub starsUsed in 2 repos~5.1k tokens
Agent WorkflowsAuto-check passed
Claude Code Agent Development
anthropics/claude-plugins-official
Official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
38k GitHub starsUsed in 8 repos~2.8k tokens
Agent WorkflowsAuto-check passed
Skill Creator
Azure/azqr
Official
Create new skills, modify and improve existing skills, and measure skill performance.
795 GitHub starsUsed in 89 repos~8.2k tokens
Agent WorkflowsAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo

Latex Posters
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
145 GitHub stars~1.5k tokensUpdated 9 days ago
Auto-check: notes
Skill Creator
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
145 GitHub stars~4.4k tokensUpdated 9 days ago
Auto-check passed
DOCX
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
145 GitHub stars~1.2k tokensUpdated 9 days ago
Auto-check passed
PDF
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
145 GitHub stars~488 tokensUpdated 9 days ago
Auto-check passed
Init Project Orchestration
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
145 GitHub stars~1.6k tokensUpdated 9 days ago
Auto-check passed
Pre Commit Audit
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
145 GitHub stars~2.8k tokensUpdated 9 days ago
Auto-check: notes

Questions about Skill Preflight

What does Skill Preflight do?

Deliver a pre-flight duplicate check before creating new skills or agents. Skill Preflight is an agent skill from flonat/flonat-research. Deliver a pre-flight duplicate check before creating new skills or agents.

When should I use Skill Preflight?

Skill Preflight fits situations like: the user requests a pre-flight duplicate check before creating new skills.

How do I install Skill Preflight in Claude Code?

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

How do I install Skill Preflight in Codex?

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

Can I use Skill Preflight 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 flonat/flonat-research --skill skill-preflight -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-preflight, .gemini/skills/skill-preflight, .github/skills/skill-preflight and .opencode/skills/skill-preflight in your project.

What does Skill Preflight need to run?

SKILL.md names no scripts, command-line tools or credentials: Skill Preflight is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Glob, Grep, AskUserQuestion.

Does Skill Preflight 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 Skill Preflight 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 Skill Preflight use?

Skill Preflight 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 Skill Preflight use?

About 2.1k tokens (SKILL.md is roughly 8.6k 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 Skill Preflight?

Skills that share tags, products or a category with Skill Preflight: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Preflight?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

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

Install Skill Preflight

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Creation Guard: Pre-Flight Duplicate Check

When to Use

Process

Step 1: Identify the Proposal

Step 2: Search Existing Artifacts

Step 3: Analyse Overlap

Step 4: Generate Recommendation

Step 5: Present and Confirm

Output Format

Recommendation Details

PROCEED

EXTEND

COMPOSE

ITERATE

BLOCK

Post-Match Action Table

Self-Check Questions

Naming Convention Enforcement

Anti-Patterns

Integration

Files

Compare with similar skills

Similar skills

More from flonat/flonat-research

Related

Questions about Skill Preflight