CONTRIBUTING.md

Contributing

How this repo works

Synced skills are owned by the library they document. Libraries host those skills at <package-dir>/.agents/skills/<skill-name>/; this repo is a thin aggregator that mirrors them to two destinations:

• plugins/<plugin>/skills/<skill>/ — for the Claude Code plugin marketplace.
• skills/<skill>/ — the standalone copy for agentskills.io.

Skill	Upstream
logfire-setup	pydantic/logfire — logfire/.agents/skills/logfire-setup/
logfire-instrumentation	pydantic/logfire — logfire/.agents/skills/logfire-instrumentation/
logfire-infrastructure	pydantic/logfire — logfire/.agents/skills/logfire-infrastructure/
logfire-evals	pydantic/logfire — logfire/.agents/skills/logfire-evals/
building-pydantic-ai-agents	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/building-pydantic-ai-agents/
migrating-agno-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-agno-to-pydantic-ai/
migrating-claude-agent-sdk-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-claude-agent-sdk-to-pydantic-ai/
migrating-google-adk-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-google-adk-to-pydantic-ai/
migrating-langchain-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-langchain-to-pydantic-ai/
migrating-mastra-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-mastra-to-pydantic-ai/
migrating-openai-agents-sdk-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-openai-agents-sdk-to-pydantic-ai/
migrating-pi-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-pi-to-pydantic-ai/
migrating-vercel-ai-sdk-and-eve-to-pydantic-ai	pydantic/pydantic-ai — pydantic_ai_slim/pydantic_ai/.agents/skills/migrating-vercel-ai-sdk-and-eve-to-pydantic-ai/
pydantic-ai-harness	pydantic/pydantic-ai-harness — pydantic_ai_harness/.agents/skills/pydantic-ai-harness/
pydantic	pydantic/pydantic — .agents/skills/pydantic/

A daily workflow (.github/workflows/sync-from-upstream.yml) clones each upstream listed above, runs rsync -a --delete into both destinations, and opens a PR. CI (scripts/check-skill-sync.sh) enforces that plugin and standalone skill copies stay byte-identical.

Anything you add directly inside a synced skill directory will be wiped on the next sync. To change synced skill content, send a PR upstream. Everything else in this repo (plugin metadata, repo-root files, .github/, scripts/) is fine to edit here.

Adding a new skill

1. Ensure the skill exists in the library at <package-dir>/.agents/skills/<skill-name>/.
2. Add a sync_skill entry to scripts/sync-from-upstream.sh.

Manually triggering a sync

Actions → Sync skills from upstream → Run workflow.

Plugin development

Test a Claude Code plugin locally:

claude --plugin-dir ./plugins/logfire

After editing a Codex plugin, reload the plugin cache:

./scripts/reload-codex-plugin.sh logfire
./scripts/reload-codex-plugin.sh logfire-exporter

A new Codex conversation may be required for plugin metadata, skills, MCP servers, icons, or hooks to refresh.

While developing the Cursor plugin, symlink the checkout instead of copying it:

ln -s /absolute/path/to/pydantic/skills/plugins/logfire ~/.cursor/plugins/local/logfire

Host-specific metadata lives alongside the shared plugin content:

.claude-plugin/marketplace.json
.cursor-plugin/marketplace.json
.agents/plugins/marketplace.json
plugins/logfire/.claude-plugin/plugin.json
plugins/logfire/.cursor-plugin/plugin.json
plugins/logfire/.codex-plugin/plugin.json
plugins/logfire-exporter/.codex-plugin/plugin.json

The Cursor and Codex marketplaces currently list logfire; Codex also lists logfire-exporter. The ai and pydantic plugins remain Claude-only plus a standalone cross-agent skill each.