project

Redirect skill discovery from a placeholder to numbered project skill documents.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill project-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/project
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill project-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents discovery parsers and operators from treating this project directory as the real location of actionable content when the actual skills live in numbered subdirectories.

Core Features & Use Cases

  • Discovery Redirect: Provides a stable project skill entry point with an accurate explanation of where the actual skills have moved.
  • Numbered Skill Referencing: Names the specific moved skills so a reader or tooling can locate the authoritative markdown sources quickly.
  • Parser Compatibility: Keeps the SKILL.md root requirement satisfied for systems that expect a project-named skill directory.

Quick Start

Ask the AI to summarize the three linked trust-plane skills by reading the target numbered markdown files referenced in this skill.

Frequently Asked Questions about project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I redirect skill discovery away from a placeholder project directory to actual markdown files?

To redirect skill discovery, use a placeholder root skill directory that satisfies the mandatory SKILL.md YAML frontmatter requirements while explicitly enumerating the moved skill targets in numbered subdirectories for deterministic retrieval.

Why does my repository indexing parser fail when the project skills are in numbered subdirectories?

Repository indexing parsers fail when they expect a project-named root skill directory but find only numbered subdirectories. A redirect entry point satisfies this root requirement and points parsers to the authoritative markdown sources.

What is the best way to satisfy the mandatory SKILL.md YAML frontmatter requirement for a project directory?

The best way to satisfy the SKILL.md YAML frontmatter requirement is to maintain a stable project-named entry point that provides parser compatibility while explaining where the actual actionable skills have moved.

Can I use a redirect entry point to manage skill discovery for automated documentation generation?

Yes, you can use a redirect entry point during automated documentation generation and repository indexing to prevent treating the project directory as the real location of actionable content.

How to quickly locate authoritative markdown sources when skills are moved to numbered directories?

Quickly locate authoritative markdown sources by reading the specific moved skill targets enumerated within the redirect skill's documentation, ensuring deterministic discovery of the numbered markdown files.

Does a placeholder project skill entry point work with automated retrieval and parser systems?

Yes, a placeholder project skill entry point works with automated retrieval systems by keeping the root SKILL.md requirement satisfied and naming the specific moved skills for tools to locate.