Preflight
Use before editing code to inspect project state and constraints.
Install
$ agentstack add skill-mverab-slashstack-skills-preflight ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mverab-slashstack-skills-preflight) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- Respond in the user's language. If the user writes Spanish, answer in Spanish.
- Explain what just happened: state that SlashStack added local agent guidance files and did not change app code.
- Inspect git status: current branch, uncommitted changes, recent commits, and dirty working tree.
- Inspect installed SlashStack skills: list the skills folder found, count the
SKILL.mdfiles, and name the installed skills. - Discover constraints: identify the test command, build command, lint command, and project conventions from
.agents/memory/project.mdor project files. - 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.
- 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.
- Avoid jargon. Explain risks in beginner-friendly language without hiding exact commands or file paths.
- 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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mverab
- Source: mverab/slashstack-skills
- License: MIT
- Homepage: https://slashstack.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.