Skills and project instructions

A skill is a folder containing SKILL.md with instructions for a particular kind of work. Redcast reads skills from your existing agent folders instead of requiring a separate catalog.

Discovery orderCopy Anchor Link

Redcast looks in:

1. <agent folder>/.agents/skills
2. ~/.agents/skills
3. ~/.config/agents/skills
4. ~/.claude/skills

A project-local skill takes precedence over a global skill of the same name. Skills are discovered when the agent editor opens or a turn starts; launching Redcast does not scan all these folders.

Choose what an agent can seeCopy Anchor Link

Open the agent editor's skills section. It lists the name, description and folder for each discovered skill.

• All skills makes discovered skills available except those you switch off. Newly discovered skills are included.
• Only selected makes just your chosen skills available. A new skill stays out until you select it.

The selection applies to the native prompt's skill list, load_skill, and an ACP agent's initial briefing. It is a way to keep a specialized agent focused: a release-writing agent may need only your changelog and style skills.

Create a project skillCopy Anchor Link

Create a directory such as .agents/skills/release-notes/ in the agent's working folder and add:

---
name: release-notes
description: Write user-facing release notes from the project's Git changes.
---
Read the commits since the previous release.
Group changes by the workflow they improve.
Use the product's actual command and setting names.
Do not describe unfinished roadmap items as shipped features.

Keep supporting examples or templates beside SKILL.md and refer to them by a clear relative path. Reopen the editor or start a new turn to discover changes.

AGENTS.md and memoryCopy Anchor Link

AGENTS.md belongs to the working folder and supplies project-wide instructions. A skill is loaded for a particular job. The agent's Memory tools keep its own notes across work. These serve different purposes; repeating the same instructions in all three can make them contradict each other.

TroubleshootingCopy Anchor Link

If a skill is missing, check the folder location, SKILL.md name and selection mode. If the wrong version loads, check for a project skill with the same name. If a skill asks for an unavailable tool, enabling the skill does not automatically enable that tool family or grant permissions.