Skip to content

Own maintained skills directly in the plugin marketplace #618

Description

@devantler

🤖 Generated by the Agentic Engineer

Objective

Merge the maintained agent-skills sources into their plugins so one repository owns authoring, validation and delivery.

Details

Part of devantler-tech/monorepo#4742. The maintainer explicitly requested retiring the separate skills repository. Preserve every in-house skill and its resources, bring the source behavioral checks with them, and retain external provenance, update behavior and edit guards.

Checklist

  • Every maintained skill is authored in its appropriate plugin, including the currently unbundled documentation introduction skill.
  • Local skills are skipped safely by upstream refresh; external skills remain protected against hand edits and provenance stripping.
  • Behavioral and specification checks, license records, plugin manifests, versions and release notes cover the merged source.
  • Installation, authoring guidance and consumer paths point to agent-plugins.
  • Current-head CI, substantive review, merge and delivery readback pass.

Dependencies

Complete this before monorepo adoption and archival of agent-skills.

Activity

  1. coderabbitai commented on Nov 1, 2026

    @coderabbitai
    🔗 Related PRs

    #595 - chore: record the license of every bundled third-party skill [merged]
    #613 - chore: adopt the Marketplace skill updater [merged]
    #604 - fix(updater): sign generated skill metadata with the existing App [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Nov 1, 2026
  3. added 2 commits that reference this issue on Nov 1, 2026
  4. moved this from 🏃🏻‍♂️ In Progress to ✅ Done in 🌊 Project Boardon Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    No fields configured for Refactor.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions