Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gofastskill.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

FastSkill integrates seamlessly with Cursor IDE to provide AI agents with access to a comprehensive skill registry. This enables Cursor’s AI to discover and utilize specialized tools and workflows automatically.
Cursor integration uses AGENTS.md. Run fastskill sync to sync installed skills — fastskill automatically detects the correct metadata file for your agent (AGENTS.md for Cursor, CLAUDE.md for Claude Code, GEMINI.md for Gemini). Use --agent cursor-agent to target Cursor explicitly.

​
How It Works

​
1. Sync skills to AGENTS.md (Cursor)

Expose installed skills to Cursor by syncing them into AGENTS.md. Cursor uses AGENTS.md as its instruction file; fastskill auto-detects this when AGENTS.md exists: 
# Sync all installed skills to AGENTS.md (non-interactive)
fastskill sync --yes

# Or run interactively to choose which skills to expose
fastskill sync
For semantic search over skills, index the skills directory: 
fastskill reindex --skills-dir .claude/skills/

​
3. Cursor integration

Cursor reads AGENTS.md and native skills/agents configuration to discover available skills.

​
Configuration

​
Basic setup

Ensure your project has a skill-project.toml with [tool.fastskill] and a skills_directory. Then run: 
fastskill sync --yes
This updates AGENTS.md with the list of installed skills so Cursor (and other agents) can discover them. Use fastskill sync without --yes to choose which skills to expose interactively.

​
AGENTS.md format

fastskill sync writes a <skills_system> section into the detected metadata file (AGENTS.md for Cursor) with <available_skills> listing each skill’s id, description, and location (project or global). Cursor and other agents that read AGENTS.md use this to discover and invoke skills (e.g. via fastskill read <skill-id>).

​
How Cursor uses the skills

​
Tool discovery

When you ask Cursor to perform a task, it:
  1. Reads available skills from AGENTS.md (Cursor’s instruction file) and native Cursor skills/agents
  2. Matches task requirements against skill descriptions
  3. Identifies relevant skills for the task
  4. Provides access to the full SKILL.md content via fastskill read <skill-id>

​
Example Usage

User Query: “Help me create a PowerPoint presentation for my quarterly review” Cursor Process:
  1. Scans skills registry for “presentation” or “powerpoint” related skills
  2. Finds relevant skills (pptx, presentation-tools, etc.)
  3. Accesses full SKILL.md content for implementation details
  4. Provides step-by-step guidance using the skill

​
Context Awareness

Cursor can now understand:
  • Available tools: What skills are installed
  • Skill capabilities: What each skill can do
  • Usage patterns: How to combine multiple skills
  • Implementation details: Specific instructions and parameters

​
Advanced Configuration

​
Agent detection

fastskill sync automatically detects which metadata file to use by scanning the project directory for known files in this order: AGENTS.md, CLAUDE.md, GEMINI.md. The first file found is used. If none exist, AGENTS.md is created.
AgentMetadata fileAgent key
CursorAGENTS.mdcursor-agent
Claude CodeCLAUDE.mdclaude
Google GeminiGEMINI.mdgemini
GitHub Copilot(unsupported — use --agents-file)copilot
To target Cursor explicitly regardless of what files exist: 
fastskill sync --yes --agent cursor-agent
To write to a completely custom path: 
fastskill sync --yes --agents-file custom.md

​
Multiple Skill Directories

# Index multiple directories
fastskill reindex --skills-dir .claude/skills/
fastskill reindex --skills-dir ./custom-skills/

# Or use different output files
# Configure separate exports for each directory

​
Choosing which skills to sync

Run fastskill sync without --yes to interactively select which installed skills appear in the detected metadata file.

​
Automation

​
GitHub Actions

Update skills metadata when skills change: 
# .github/workflows/update-skills.yml
name: Update skills metadata
on:
  push:
    paths:
      - '.claude/skills/**'
      - 'skill-project.toml'

jobs:
  update-agents:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install FastSkill CLI
        run: |
          # Add the steps your org uses to place `fastskill` on PATH (release tarball, package, etc.)
          fastskill -V

      - name: Sync skills to metadata file
        run: fastskill sync --agent cursor-agent --yes

      - name: Commit metadata file
        run: |
          git config --global user.name 'github-actions[bot]'
          git config --global user.email 'github-actions[bot]@users.noreply.github.com'
          git add AGENTS.md
          git commit -m 'chore: update AGENTS.md skills' || echo "No changes"
          git push

​
Pre-commit hooks

#!/bin/bash
# .git/hooks/pre-commit
if git diff --cached --name-only | grep -q ".claude/skills/"; then
    echo "Skills changed, syncing metadata file..."
    fastskill sync --agent cursor-agent --yes
    git add AGENTS.md
fi

​
Troubleshooting

​
Common Issues

​
AGENTS.md not updated

# Ensure skill-project.toml and skills directory exist
cat skill-project.toml
ls -la .claude/skills/  # or your configured skills_directory

# Sync manually
fastskill sync --yes

​
Cursor not recognizing skills

# Ensure AGENTS.md exists and contains a skills section
cat AGENTS.md | head -80

# Re-sync installed skills
fastskill sync --yes

​
Outdated skill list

fastskill sync --yes

​
Debug Commands

# Check FastSkill configuration
fastskill --help

# Test search functionality
fastskill search "test query" --embedding false

# Verify index exists
ls -la .claude/skills/.fastskill/index.db

# Check detected metadata file
wc -l AGENTS.md

​
Performance Considerations

​
File Size

  • Small repositories: < 10KB
  • Medium repositories: 50-200KB
  • Large repositories: 500KB+

​
Generation Time

  • Small: < 5 seconds
  • Medium: 10-30 seconds
  • Large: 1-5 minutes

​
Update Frequency

  • On-demand: Update when skills change
  • Scheduled: Daily/weekly regeneration
  • Event-driven: Update on git push to skills directory

​
Integration Patterns

​
Multi-environment setup

Use different files per environment via --agents-file: 
fastskill sync --yes --agents-file AGENTS-dev.md
fastskill sync --yes --agents-file AGENTS-prod.md

​
Team Collaboration

Share skills registry across team: 
# Generate team-wide registry
markdown_export:
  output_path: "docs/team-skills.md"
  header_instructions: |
    Team Skills Registry - Updated $(date)
    This file contains all skills available to the development team.

​
Documentation Integration

Include in project docs: 
# Generate for docs site
markdown_export:
  output_path: "docs/skills/index.md"
  header_instructions: |
    # Available Skills

    This page lists all skills available in the project.

​
Future Enhancements

​
Planned Features

  • Filtered exports: Export only skills relevant to specific projects
  • Version tracking: Track skill versions and changes
  • Dependency mapping: Show skill relationships and dependencies
  • Usage analytics: Track which skills are most used
  • Collaborative editing: Allow team members to contribute skill updates

​
Custom Templates

Allow custom markdown templates: 
markdown_export:
  template: "custom-template.md"
  variables:
    project_name: "My Project"
    team: "Engineering"

​
Summary

FastSkill’s Cursor integration provides: ✅ Automatic skill discovery for AI agents ✅ Seamless integration with existing workflows ✅ Up-to-date documentation through automated generation ✅ Performance optimized for large skill repositories ✅ Flexible configuration for different use cases The integration bridges the gap between static skill definitions and dynamic AI agent capabilities, enabling Cursor to provide more intelligent and context-aware assistance.