Skip to main content
Skill delivery lets you create custom Claude Code skills and automatically distribute them to every developer machine in your organization. Skills appear as native slash commands in Claude Code — developers can invoke them manually or Claude can invoke them automatically based on context.

​
What Are Skills?

Skills are Claude Code extensions that define workflows, guidelines, and tools. They’re written as Markdown files with YAML frontmatter and can include:
  • Code review checklists that Claude follows when reviewing PRs
  • Deployment procedures with step-by-step instructions
  • API design guidelines that Claude applies when writing endpoints
  • Security audit workflows that trigger automatically when discussing vulnerabilities
  • Anything else you want Claude to know or do consistently across your team

​
How It Works

1

Admin uploads a skill

Upload a skill package (.tar.gz) in the dashboard under Rules Engine > Skills.
2

Skill is encrypted and stored

The skill is encrypted with your organization’s key and stored securely.
3

Agents sync the skill

Within 15 minutes, every Turen agent downloads and deploys the skill to ~/.claude/skills/turen/.
4

Developers use the skill

Claude Code discovers the skill natively. Developers see it in their / command menu and Claude can invoke it automatically.

​
Creating a Skill

A skill is a .tar.gz archive containing a SKILL.md file with YAML frontmatter: 
---
name: security-review
description: >
  Security-focused code review guidelines. Use when reviewing
  code, auditing security, or when asked about vulnerabilities.
user-invocable: true
allowed-tools: Read, Grep, Glob
---

## Security Review Checklist

When reviewing code for security issues, always check for:

### Input Validation
- [ ] All user input is validated and sanitized
- [ ] SQL queries use parameterized statements
- [ ] File paths are validated against traversal attacks

### Authentication
- [ ] Passwords are hashed with bcrypt/argon2
- [ ] Session tokens have proper expiry
- [ ] API keys are not hardcoded

### Data Protection
- [ ] Sensitive data is encrypted at rest
- [ ] PII is not logged
- [ ] Secrets are loaded from environment variables

​
Frontmatter Options

FieldRequiredDescription
nameYesSkill identifier — becomes the /slash-command name
descriptionYesWhen to use the skill. Claude uses this to decide when to auto-invoke.
user-invocableNoIf true (default), appears in the / command menu
disable-model-invocationNoIf true, only the developer can invoke it — Claude won’t auto-invoke
allowed-toolsNoRestrict which tools Claude can use (e.g., Read, Grep, Glob)

​
Supporting Files

Skills can include additional files alongside SKILL.md. For example, a deployment skill might include a checklist: 
deployment-guide/
├── SKILL.md
└── checklist.md
The SKILL.md can reference these files and Claude will have access to them.

​
Uploading a Skill

1

Package the skill

Create a .tar.gz archive containing your SKILL.md and any supporting files.
tar -czf security-review.tar.gz SKILL.md
2

Open the Skills page

In the dashboard, navigate to Rules Engine > Skills.
3

Upload

Click Upload Skill and select your .tar.gz file. The dashboard validates the package and extracts the skill metadata.
The skill is now queued for delivery. Agents will pick it up within 15 minutes.

​
Managing Skills

From Rules Engine > Skills, you can:
  • Enable/disable — Toggle whether a skill is delivered to agents
  • Edit — Update the skill name, description, or upload new content
  • Version history — View all previous versions with the ability to restore any version
  • Delete — Remove a skill from all agent machines

​
Curated Skills

Turen provides a set of pre-built skills created by the Turen team. These cover common use cases and can be enabled with a single click. Curated skills appear in a separate tab from your custom skills.

​
Versioning

Every time you upload or edit a skill, a new version is created. The dashboard shows the full version history with:
  • Version number
  • Content hash
  • File size
  • Who made the change and when
  • A Restore button to roll back to any previous version

​
What Developers See

Once a skill is deployed, developers see it natively in Claude Code: Manual invocation: 
> /security-review src/auth.js
Auto-invocation — if the skill’s description matches the conversation context, Claude invokes it automatically: 
Developer: "Review this code for vulnerabilities"
Claude: [automatically loads security-review skill]
Skills appear seamlessly alongside Claude Code’s built-in commands. Developers don’t need to install or configure anything.

​
Use Cases

Code Review Standards

Define what Claude should check during code reviews — security, performance, style, accessibility.

Deployment Procedures

Step-by-step checklists that Claude follows when helping with deployments.

API Design Guidelines

Enforce consistent API patterns, naming conventions, and error handling across your team.

Onboarding Guides

Help new developers navigate the codebase with context Claude can reference.

​
Security

  • Skills are encrypted with your organization’s unique key (AES-256-GCM) before storage
  • Only agents authenticated with your organization’s credentials can download skills
  • Skills are written to a dedicated ~/.claude/skills/turen/ directory — they cannot overwrite developer-created skills
  • All skill changes are logged in the audit trail