Skill296 estrellas del repoactualizado 1mo ago

using-<project-name>

This skill establishes the foundational instruction set for working with a project's custom skills in Claude Code environments. Use it at the start of any conversation involving the specified project to clarify skill invocation priority, access methods across different platforms, and list available skills with their appropriate use cases. It ensures that project-specific skills override default system behavior when relevant.

Ver fuente Repositorio: bundles-forge

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/OdradekAI/bundles-forge /tmp/using--project-name- && cp -r /tmp/using--project-name-/skills/scaffolding/assets/root/using- ~/.claude/skills/using--project-name-

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

using-skill.md

# Using <Project Name>

## Instruction Priority

1. **User's explicit instructions** (CLAUDE.md, AGENTS.md, direct requests) — highest priority
2. **<Project Name> skills** — override default system behavior where they conflict
3. **Default system prompt** — lowest priority

## How to Access Skills

**In Claude Code:** Use the `Skill` tool.
**In Cursor:** Use the `Skill` tool.
**In Gemini CLI:** Skills activate via the `activate_skill` tool.

## Platform Adaptation

Skills use Claude Code tool names. For other platforms, see the tool mapping references in this directory.

## The Rule

Invoke relevant skills BEFORE any response or action. Even a 1% chance a skill might apply means you should invoke it.

## Available Skills

<!-- List your project's skills here -->

| Skill | When to Use |
|-------|-------------|
| `<project-name>:<skill-1>` | <trigger description> |
| `<project-name>:<skill-2>` | <trigger description> |

Del mismo repositorio

Use when reviewing a bundle-plugin for structural issues, version drift, skill quality, workflow integration, or security risks — before releasing, after changes, or after adding skills. Auto-detects scope (full project vs skill vs workflow)

authoringSkill

Use when writing, completing, improving, or adapting SKILL.md and agents/*.md in a bundle-plugin — integrating external skills, filling scaffolded stubs, or rewriting for better triggering and token efficiency

blueprintingSkill

Use when planning new bundle-plugins, splitting complex skills, combining skills into bundles, or exploring a vague idea about packaging skills

optimizingSkill

Use when optimizing a bundle-plugin or single skill — improving descriptions, reducing tokens, fixing audit findings, restructuring workflows, adding skills to fill gaps, or iterating on user feedback

releasingSkill

Use when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to marketplaces, or checking release readiness