migrate-skills-yaml

Old format (single flat file)

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "migrate-skills-yaml" with this command: npx skills add posthog/context-mill/posthog-context-mill-migrate-skills-yaml

Old format (single flat file)

shared_docs:

skills:

New format (separate files per group)

Skills live in transformation-config/skills/ , one file per group:

integration-skills.yaml (type: example)

type: example template: integration-skill-description.md description: PostHog integration for {display_name} applications shared_docs:

feature-flag-skills.yaml (type: docs-only)

type: docs-only template: feature-flag-skill-description.md description: PostHog feature flags for {display_name} applications tags: [feature-flags] shared_docs:

Other group files

  • llm-analytics-skills.yaml -- LLM observability skills

  • logs-skills.yaml -- Log capture skills

  • other-skills.yaml -- Catch-all (e.g. HogQL); variants can override template and shared_docs

Existing groups

File Plugin name Type Category suffix

integration-skills.yaml

posthog-integration

example

-integration

feature-flag-skills.yaml

posthog-feature-flags

docs-only

-feature-flag

llm-analytics-skills.yaml

posthog-llm-analytics

docs-only

-llm-analytics

logs-skills.yaml

posthog-logs

docs-only

-logs

other-skills.yaml

posthog-tools

docs-only

(none)

Key differences from old format

  • variants (not variations ) is the key for the list of skills

  • type is set at the group level, not per-skill (unless a variant needs to override)

  • template is set at the group level; each group has its own SKILL.md template

  • shared_docs can be set at group level (shared by all variants) or per-variant

  • description at group level uses {display_name} placeholder, substituted per variant

  • tags at group level are merged with per-variant tags

  • Skill IDs are automatically namespaced: {id}-{category} (e.g. nextjs-app-router in integration-skills becomes nextjs-app-router-integration ). The other category skips the suffix.

Migration steps

  • Identify which group each skill belongs to (integration, feature-flag, llm-analytics, logs, or other)

  • Add each skill as a variant in the appropriate transformation-config/skills/{group}-skills.yaml file

  • Remove type from the variant (inherited from group) unless it needs to differ

  • Keep id , display_name , description (optional), tags , docs_urls , and example_paths (for example-type skills)

  • Remove the old flat file

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

posthog-instrumentation

No summary provided by upstream source.

Repository SourceNeeds Review
General

hogli

No summary provided by upstream source.

Repository SourceNeeds Review
General

setup-web-tests

No summary provided by upstream source.

Repository SourceNeeds Review