Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Preflight

ASecurity

Use before editing code to inspect project state and constraints.

4 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add mverab/slashstack-skills --skill preflight --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Preflight?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Preflight
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mverab-preflight/badge)](https://www.skillsdirectory.com/skills/mverab-preflight)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: preflight
description: Use before editing code to inspect project state and constraints.
---

# Preflight

## Purpose

Inspect repo state before coding, in beginner-friendly language.

## When to Use

Use before editing code to inspect project state and constraints.

## Workflow

1. Respond in the user's language. If the user writes Spanish, answer in Spanish.
2. Explain what just happened: state that SlashStack added local agent guidance files and did not change app code.
3. Inspect git status: current branch, uncommitted changes, recent commits, and dirty working tree.
4. Inspect installed SlashStack skills: list the skills folder found, count the `SKILL.md` files, and name the installed skills.
5. Discover constraints: identify the test command, build command, lint command, and project conventions from `.agents/memory/project.md` or project files.
6. Flag risks with severity:
   - High: wrong branch, uncommitted changes that will conflict, failing tests on main.
   - Medium: missing tests for the target area, unknown build/lint commands.
   - Low: stale references in `.agents/references/`, unused dependencies, thin project memory.
7. Modo Aprendiz: for EACH risk item, include three sub-fields in beginner-friendly Spanish:
   - Qué significa: what the risk means in plain language.
   - Por qué importa: why it matters for the project.
   - Qué hacer ahora: one concrete action to take now.
8. Avoid jargon. Explain risks in beginner-friendly language without hiding exact commands or file paths.
9. Do not edit files, run fixes, deploy, or change configuration.

## Output

Use exactly these sections:
- What just happened: one short explanation of what SlashStack installed and what it did not change
- SlashStack installed: skills folder, number of skills, installed skill names
- Project state: branch, commits, uncommitted changes
- Commands detected: test, build, lint
- Risks: High / Medium / Low items with plain-language impact and recommended action; each item includes Qué significa, Por qué importa, and Qué hacer ahora
- What to do now: one concrete safest next step
- Exact next prompt: one copy-paste prompt the user can send next

Attribution

mverabmverab
View sourceSee grades on GitHubMore from mverab →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →