Docs / Agents
Skills
Create, import and maintain reusable agent procedures, with team or personal scope.
A skill packages instructions and optional supporting files for a concrete task. The agent reads a matching skill when it needs that procedure. Having a skill does not grant cloud access: its operations still use the selected credentials and the provider's permissions.
Built-in, team and personal skills
Pangea ships built-in skills. Open Settings → Skills to review your team's skills and your personal ones.
- Team skills are shared with everyone in the team.
- Personal skills belong to you. Use Move to team skills to share one with the team.
You can ask the agent to write a team skill after it finishes a repeatable task. Review what it will save and the scope. Keep commands, prerequisites, checks and recovery steps together. Refer to configured credentials instead of putting secret values in the files.
Only team Administrators can delete team skills.
Import and install
- Import from this computer brings in skills from
~/.claude/skillsor~/.agents/skills. Review each skill's files before you import it. - Install from GitHub installs skills from a GitHub repository. Check for updates later shows which installed skills changed upstream.
- Sync my setup, under Settings → My preferences, keeps your local Claude Code skills in sync as personal skills. See Instructions.
A skill can run powerful operations. Don't import an unreviewed procedure just because its name matches your task.
Maintain
Edit a skill when its commands or assumptions change. Changes reach the runtime at its next turn. Sharing a skill with the team does not copy a computer's private CLI sign-ins or repository files.
Instructions, skills and memory
Use instructions for standing preferences and team rules, a skill for a procedure, and memory for durable facts and verified findings. A skill's actions follow permission modes. Significant cloud work may use a plan, but not every skill run creates one.