Posit Skills — Skill-Repo Conventions & Registration
A complete, transferable playbook for a skills repository: the directory contract, the SKILL.md frontmatter, the token/line budget, the…
- Type
- CLAUDE.md Example
- Repository
- posit-dev/skills
- GitHub stars
- 525
- License
- MIT
- Repo last updated
- Sep 18, 2026
- Source file
- CLAUDE.md
What Posit Skills — Skill-Repo Conventions & Registration is
Posit Skills — Skill-Repo Conventions & Registration is a claude.md example published in the posit-dev/skills repository on GitHub, which has about 525 stars. The repository describes itself as: “A collection of Claude Skills from Posit”
A CLAUDE.md file holds standing instructions that Claude Code reads at the start of every session in a project, such as conventions, commands, and rules. Examples like Posit Skills — Skill-Repo Conventions & Registration show how other teams structure theirs.
In Claude Cowork, the equivalent places for this kind of guidance are your global instructions, project instructions, and folder instructions.
How to install Posit Skills — Skill-Repo Conventions & Registration
Claude Code
- Copy the parts that fit your project into CLAUDE.md at the project root, or into ~/.claude/CLAUDE.md for rules that apply everywhere.
- Keep it short and specific; remove anything that doesn't match how your team works.
Claude Cowork
- Put personal rules in Settings → Instructions for Claude (global instructions).
- Put project or folder rules in the project's instructions or the folder instructions for that directory.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from CLAUDE.md, shared under the repository's MIT license. Read the full file on GitHub.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Repository Is
A collection of Claude Skills published by Posit PBC. Skills are structured markdown files that teach Claude specialized workflows (e.g., Shiny app development, R package testing, GitHub PR workflows). There is no application code to build, compile, or deploy — the primary artifacts are Markdown files consumed directly by Claude's skill system.
Utility Script
The only runnable utility is count-skill-tokens.py, which reports line and token counts for a skill:
# Requires uv
./count-skill-tokens.py shiny/shiny-bslib
# or
uv run count-skill-tokens.py r-lib/cliWarns when SKILL.md exceeds 5,000 tokens / 500 lines, or when the skill description frontmatter exceeds 100 tokens.
Directory Structure
<category>/
README.md # Category-level notes (optional per skill)
<skill-name>/
SKILL.md # Required: skill definition with YAML frontmatter
references/ # Optional: supplementary docs loaded on demand
*.md
scripts/ # Optional: R or shell helpers
templates/ # Optional: document templatesDo not create a README.md inside individual skill directories — documentation about a skill's design goes in the category README.
SKILL.md Format
Every skill requires YAML frontmatter at minimum:
---
name: your-skill-name # kebab-case, matches directory name
description: > # Claude reads this to decide when to activate the skill
Clear description of what this skill does and when to trigger it.
Keep under 100 tokens.
---The body is instructions written for Claude, not end users — imperative, step-by-step, covering edge cases.
Registering a New Skill
After creating the skill directory, add it to the appropriate plugin in .claude-plugin/marketplace.json:
{
"name": "open-source",
"skills": [
"./open-source/release-post",
"./open-source/your-new-skill" ← add here
]
}If a skill spans multiple categories (like brand-yml for both Shiny and Quarto), add its path to multiple plugin skills arrays. The source field is always "./" (repo root).
When adding a new plugin to marketplace.json, also update the root README.md "Method 2: Direct Installation" section so it lists the /plugin install command for every plugin. All plugins in marketplace.json must have a corresponding install line in the README.
Skill Categories
Key Conventions
- Progressive disclosure: Put specialized or large reference content in references/*.md and instruct Claude to read those files only when needed. This keeps the main SKILL.md within token limits.
- R scripts: Use a shebang (#!/usr/bin/env Rscript), include inline usage docs, check for required packages at startup, and exit non-zero on error.
- Testing: Install locally via cp -r / ~/.config/claude-code/skills/ and verify Claude activates the skill in Claude Code.
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Posit Skills — Skill-Repo Conventions & Registration?
Posit Skills — Skill-Repo Conventions & Registration is a claude.md example for Claude Code and Claude Cowork from the posit-dev/skills repository on GitHub. A complete, transferable playbook for a skills repository: the directory contract, the SKILL.md frontmatter, the token/line budget, the…
How do I install Posit Skills — Skill-Repo Conventions & Registration in Claude Code?
Copy the parts that fit your project into CLAUDE.md at the project root, or into ~/.claude/CLAUDE.md for rules that apply everywhere. Keep it short and specific; remove anything that doesn't match how your team works.
Can I use Posit Skills — Skill-Repo Conventions & Registration in Claude Cowork?
Put personal rules in Settings → Instructions for Claude (global instructions). Put project or folder rules in the project's instructions or the folder instructions for that directory.
Is Posit Skills — Skill-Repo Conventions & Registration safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Alt Text Generate and improve accessible alt text for data visualizations and images in R packages and Quarto documents. Use when the user wants to… Skill · posit-dev/skills
- Blueprint — Flows, Skills, and Unattended Loops A masterclass in structuring a multi-skill agent system in one file: three named flows (Setup / Decide / Deliver), a skill catalog, and a… CLAUDE.md Example · owainlewis/blueprint
- dbt Agent Skills — Frontmatter Rules & Error Table The most actionable take on SKILL.md frontmatter: the exact allowed fields, the lowercase-hyphen name rule, and a validation-error → fix… CLAUDE.md Example · dbt-labs/dbt-agent-skills
- Turbo — Dual-Edition Skill Monorepo Map A compact, well-annotated map of a monorepo that ships parallel Claude Code and Codex editions from one source tree. Cleanly separates… CLAUDE.md Example · tobihagemann/turbo
- Cloudflare Skill — Anti-Patterns as Code Organizes guidance around a dedicated Anti-Patterns section — SQL injection, secrets, resource cleanup, missing compatibility_date — each… CLAUDE.md Example · dmmulroy/cloudflare-skill
- Langfuse Skills — 'Only Add If It Beats the Docs' An unusually disciplined content policy for skill authors: add a use case only when it beats fetching the docs, put 'when to use' guidance… CLAUDE.md Example · langfuse/skills
- Claudeclaw — Identity & Voice as Persistent Memory A fully worked example of using CLAUDE.md as the agent's persistent identity and voice spec — Core Truths, Vibe, emoji budget, boundaries… CLAUDE.md Example · moazbuilds/claudeclaw
- OrchestKit — Source-vs-Generated Invariants Nails the single most common agent footgun in a build-step repo: a load-bearing 'edit src/, NEVER edit plugins/' invariant, spelled out… CLAUDE.md Example · yonatangross/orchestkit