Skip to main content

Stop improvising. Start executing.

Rifteo skills are the methodology layer your AI agent is missing. Each skill encodes the exact steps, bypass techniques, and output formats that expert practitioners use so your agent delivers complete, structured results from the first prompt.

34 skills

Web, API, infrastructure, compliance, attack mindset, and reporting every phase covered

★ Top 5 benchmarked

Community-selected best performers proven by real benchmark data

One command install

rifteo-skills add <skill> no config, no account
★ marks the top 5 skills by benchmark performance. See the full benchmark results →

Top skills right now

Ranked by benchmark performance — real numbers, same model, skill on vs. skill off: See full benchmark report →

What is a skill?

A skill is a self-contained instruction file that teaches an AI agent a specific security or compliance methodology. Each skill:
  • Defines precise trigger conditions: when the agent should activate it
  • Provides a step-by-step methodology the agent follows
  • Specifies the exact output format to produce
  • Includes rules and guardrails to prevent incorrect behavior
Skills are not code modules they are structured prompts that encode expert knowledge. The agent reads the SKILL.md, understands when to apply it, and executes the methodology against whatever the user provides.

Installing a skill


Available skills

Web Application API Security Infrastructure Reconnaissance Reporting Compliance Workflow Attack Mindset Integrations Skills that orchestrate external MCP tool servers into structured engagements.

Skill anatomy

Every skill lives in its own directory:

SKILL.md

The core of every skill. It has two parts: a frontmatter block and a body. Frontmatter declares the skill’s identity and discovery metadata:
Body defines the agent behavior in structured Markdown sections:

Skill lifecycle

1

Define

Identify the methodology to encode: what triggers it, what steps it follows, and what output it produces
2

Write SKILL.md

Author the SKILL.md following the Style Guide: frontmatter, trigger conditions, step-by-step instructions, output format, and rules
3

Add references and scripts

Bundle any reference documents or helper scripts the skill needs into references/ and scripts/
4

Benchmark

Run skill-benchmark to score quality and check compatibility across agents if it doesn’t outperform no-skill, it doesn’t ship
5

Document

Write the .mdx documentation page following the Style Guide
6

Publish

Open a pull request the skill appears in the community hub after review and merge

Naming conventions

Ready to contribute?

Follow the Style Guide and the contribution process to add your methodology to the community library.