Agent skill

Create Plugin

by rundeck in rundeck/rundeck

Create bundled Rundeck plugins following development standards.

Apache-2.0Auto-check passedDevOps & Cloud

Install Create Plugin

skills CLI
$ npx skills add rundeck/rundeck --skill create-plugin -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rundeck/rundeck create-plugin --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rundeck/rundeck.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-plugin .claude/skills/create-plugin && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-plugin
GitHub stars
6.3k
Token cost
~3.6k tokens
SKILL.md length
817 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create bundled Rundeck plugins following development standards.

  • Works in 8 steps: Load Context → Design Plugin → Create Plugin Structure → …
  • Tasks that involve Hooks and plugins
  • SKILL.md covers When to Use, Process, Checklist and Examples, plus 4 more sections
  • Reaches packagecloud.io; needs PKGCLD_WRITE_TOKEN and SIGNING_PASSWORD

What it does

Create Plugin is an agent skill from rundeck/rundeck. Create bundled Rundeck plugins following development standards. Auto-loads plugin development guidelines, build configuration, and release processes.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Hooks and plugins and Deployment. It works with Gradle. The repository describes itself as: Enable Self-Service Operations: Give specific users access to your existing tools, services, and scripts. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Hooks and plugins
  • Tasks that involve Deployment

Example prompts

  • “/create-plugin”

Requirements

  • A credential in GITHUB_TOKEN
  • A credential in PKGCLD_WRITE_TOKEN

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Load Context
  2. Design Plugin
  3. Create Plugin Structure
  4. Write Plugin Tests
  5. Build and Test Plugin
  6. Documentation
  7. Setup CI/CD (Optional, for standalone repos)
  8. Publishing (Optional, for open source)

What it can do on your machine

Read from SKILL.md and the folder at commit 9c3c82c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are groovy, yaml, toml, bash and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • packagecloud.io

    Also links to:

    • github.com
    • pagerduty.atlassian.net
    • docs.rundeck.com
    • docs.gradle.org
    • axion-release-plugin.readthedocs.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • PKGCLD_WRITE_TOKEN
    • SIGNING_PASSWORD
    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Plugin loads about 3.6k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 817 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rundeck/rundeck at commit 9c3c82c, republished under its Apache-2.0 licence (© rundeck). 817 words, ~3,649 tokens.

Download SKILL.mdSave it as .claude/skills/create-plugin/SKILL.md (or your agent's skills folder).
name
create-plugin
description
Create bundled Rundeck plugins following development standards. Auto-loads plugin development guidelines, build configuration, and release processes.

Create Plugin Skill

When to Use

  • Creating new bundled plugins for Rundeck
  • Adding plugin functionality to existing plugins
  • Implementing Workflow Steps, Node Steps, Resource Model Sources
  • Creating notification or logging plugins

Process

Phase 1: Load Context

Automatically read:

  • .claude/docs/plugin-development.md - Complete plugin guide
  • .claude/docs/development-guidelines.md - Code standards (@CompileStatic, Git, etc.)
  • .claude/docs/testing-guidelines.md - Plugin testing requirements
Phase 2: Design Plugin

Determine:

1. Plugin Type

  • WorkflowStep - Job step executed in workflow
  • NodeStep - Step executed on specific nodes
  • ResourceModelSource - Node source provider
  • Notification - Job notification handler
  • LogFilter - Log processing plugin
  • StorageConverter - Storage backend plugin
  • WorkflowNodeStep - Workflow step that runs on nodes

2. Service Name Use appropriate service name from ServiceNameConstants:

  • WorkflowStep - "WorkflowStep"
  • WorkflowNodeStep - "WorkflowNodeStep"
  • NodeExecutor - "NodeExecutor"
  • ResourceModelSource - "ResourceModelSource"
  • Notification - "Notification"
  • LogFilter - "LogFilterPlugin"
  • StorageConverter - "StorageConverter"

3. Plugin Properties

  • What configuration does the plugin need?
  • Which properties are required vs optional?
  • What are the default values?
Phase 3: Create Plugin Structure
Step 1: Create build.gradle

Basic Plugin build.gradle:

groovy
plugins {
    id 'groovy'
    id 'java-library'
}

// Apply shared plugin configuration
apply from: "${rootProject.projectDir}/gradle/java-plugin.gradle"

group = 'com.rundeck.plugins'
version = '1.0.0'

dependencies {
    // Rundeck core dependencies
    compileOnly "org.rundeck:rundeck-core:${rundeckVersion}"
    
    // Plugin-specific dependencies (use version properties from gradle.properties)
    implementation "com.example:library:${exampleLibraryVersion}"
    
    // Testing
    testImplementation "org.spockframework:spock-core:${spockVersion}"
}

jar {
    manifest {
        attributes(
            'Rundeck-Plugin-Version': '1.2',
            'Rundeck-Plugin-Archive': 'true',
            'Rundeck-Plugin-Classnames': 'com.example.MyPlugin',
            'Rundeck-Plugin-Name': 'my-plugin',
            'Rundeck-Plugin-Description': 'My awesome plugin'
        )
    }
}

// Copy plugin jar to output directory
task copyToLib(type: Copy) {
    from jar
    into "${rootProject.projectDir}/rundeckapp/src/main/resources/WEB-INF/rundeck/plugins"
}

build.finalizedBy copyToLib

Gradle Version Catalog:

toml
# gradle/libs.versions.toml
[versions]
rundeck = "5.4.0"
aws-sdk = "1.12.572"
spock = "2.3-groovy-3.0"

[libraries]
rundeck-core = { module = "org.rundeck:rundeck-core", version.ref = "rundeck" }
aws-s3 = { module = "com.amazonaws:aws-java-sdk-s3", version.ref = "aws-sdk" }
spock-core = { module = "org.spockframework:spock-core", version.ref = "spock" }
Step 2: Create Plugin Class

Annotate with @Plugin:

groovy
import com.dtolabs.rundeck.plugins.descriptions.Plugin
import com.dtolabs.rundeck.plugins.descriptions.PluginDescription
import com.dtolabs.rundeck.plugins.descriptions.PluginProperty
import com.dtolabs.rundeck.core.plugins.configuration.PropertyScope

@Plugin(name = "my-plugin", service = "WorkflowStep")
@PluginDescription(title = "My Plugin", description = "Does awesome things")
class MyPlugin implements StepPlugin {
    
    @PluginProperty(
        title = "API Key",
        description = "Your API key",
        required = true,
        scope = PropertyScope.Instance
    )
    String apiKey
    
    @PluginProperty(
        title = "Timeout",
        description = "Request timeout in seconds",
        defaultValue = "30"
    )
    Integer timeout
    
    @Override
    void executeStep(PluginStepContext context, Map<String, Object> configuration) {
        // Plugin implementation
        def result = doWork(apiKey, timeout)
        context.getLogger().log(2, "Result: ${result}")
    }
}

Common Annotations:

groovy
// Basic plugin definition
@Plugin(name = "plugin-name", service = "ServiceName")

// Description
@PluginDescription(title = "Display Title", description = "What it does")

// Properties
@PluginProperty(
    title = "Property Title",
    description = "What this property does",
    required = false,
    defaultValue = "default",
    scope = PropertyScope.Instance
)

// Rendering options (UI)
@RenderingOptions({
    @RenderingOption(key = "displayType", value = "PASSWORD"),
    @RenderingOption(key = "selectionAccessor", value = "STORAGE_PATH")
})

// Select values
@SelectValues(values = ["option1", "option2", "option3"])

scope — always set it explicitly: PropertyScope.Instance resolves the job/step value first, then falls back to Project, then Framework/System config. If scope is left unset, the effective default depends on the plugin type — Workflow Step / Workflow Node Step plugins (the common script-plugin case) default to PropertyScope.InstanceOnly, which resolves only the per-job value and silently ignores any Project- or System-level configuration for that property, with no error or warning. Other plugin types (Script Node Executor/File Copier, notification, resource model source, etc.) default to PropertyScope.Instance. Because this default is inconsistent and undocumented at the framework level, always declare scope = PropertyScope.Instance explicitly for any property that should be configurable above the individual job/step level — do not rely on the default. See RUN-4800 for details.

Phase 4: Write Plugin Tests

Test plugin properties:

groovy
class MyPluginSpec extends Specification {
    
    def "should have correct plugin annotations"() {
        given:
        def plugin = MyPlugin.class.getAnnotation(Plugin)
        
        expect:
        plugin.name() == "my-plugin"
        plugin.service() == "WorkflowStep"
    }
    
    def "should have required properties"() {
        given:
        def fields = MyPlugin.declaredFields
        def apiKeyField = fields.find { it.name == "apiKey" }
        def property = apiKeyField.getAnnotation(PluginProperty)
        
        expect:
        property.required() == true
        property.title() == "API Key"
    }
    
    def "should execute successfully with valid config"() {
        given:
        def plugin = new MyPlugin()
        def context = Mock(PluginStepContext)
        def config = [apiKey: "test-key", timeout: 30]
        
        when:
        plugin.executeStep(context, config)
        
        then:
        notThrown(Exception)
        1 * context.getLogger() >> Mock(PluginLogger)
    }
}
Phase 5: Build and Test Plugin
bash
# Build plugin
./gradlew :plugins:my-plugin:build

# Run tests
./gradlew :plugins:my-plugin:test

# Copy to rundeck plugins directory
./gradlew :plugins:my-plugin:copyToLib

# Check plugin was copied
ls rundeckapp/src/main/resources/WEB-INF/rundeck/plugins/
Phase 6: Documentation

README.md following Howto CLI conventions:

markdown
# My Plugin

Description of what the plugin does

## How to Build

\`\`\`bash
./gradlew build
\`\`\`

## How to Test

\`\`\`bash
./gradlew test
\`\`\`

## How to Install

\`\`\`bash
cp build/libs/my-plugin-1.0.0.jar $RDECK_BASE/libext/
\`\`\`

## How to Use

1. Create a job
2. Add "My Plugin" step
3. Configure API Key
4. Run the job

## Configuration

| Property | Required | Default | Description |
|----------|----------|---------|-------------|
| API Key  | Yes      | -       | Your API key |
| Timeout  | No       | 30      | Timeout in seconds |
Phase 7: Setup CI/CD (Optional, for standalone repos)

GitHub Actions: ./github/workflows/build.yml

yaml
name: Build

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    
    steps:
    - uses: actions/checkout@v3
    
    - name: Set up JDK 17
      uses: actions/setup-java@v3
      with:
        java-version: '17'
        
    - name: Build with Gradle
      run: ./gradlew build
      
    - name: Upload artifact
      uses: actions/upload-artifact@v3
      with:
        name: plugin-jar
        path: build/libs/*.jar

Release Workflow: .github/workflows/release.yml

yaml
name: Release

on:
  push:
    tags:
      - 'v*'

jobs:
  release:
    runs-on: ubuntu-latest
    
    steps:
    - uses: actions/checkout@v3
    
    - name: Set up JDK 17
      uses: actions/setup-java@v3
      with:
        java-version: '17'
        
    - name: Build with Gradle
      run: ./gradlew build
      
    - name: Create Release
      run: |
        gh release create \
          --generate-notes \
          --title 'Release ${{ github.ref_name }}' \
          ${{ github.ref_name }} \
          build/libs/*.jar
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Phase 8: Publishing (Optional, for open source)

PackageCloud (Preferred over JitPack; replaces Maven Central for rundeck-plugins — see RUN-4570):

Requirements:

  1. Configure a maven publishing repository pointing at https://packagecloud.io/pagerduty/rundeck-plugins/maven2 (Bearer token auth via PKGCLD_WRITE_TOKEN) — do not apply nexusPublish/nexusPublishing
  2. Add withJavadocJar() and withSourcesJar()
  3. Fix javadoc issues
  4. Sign artifacts with the real gpg CLI (not Gradle's signing plugin) and upload the .asc via curl — PackageCloud rejects Gradle's auto-generated checksum-of-signature file
  5. Configure Github secrets (PKGCLD_WRITE_TOKEN, SIGNING_KEY_B64, SIGNING_PASSWORD) and the PKGCLD_REPO_URL org variable

See: .claude/docs/plugin-development.md and the migrate-plugin-to-packagecloud skill for complete publishing setup


Checklist

Show full SKILL.md (405 more words)Show less
Plugin Development Checklist

Before considering plugin complete:

Plugin Design:

  • Plugin type selected and service name correct
  • Plugin properties identified (required vs optional)

Build Configuration:

  • build.gradle configured with correct dependencies
  • Version properties used from gradle.properties (no hardcoded versions)
  • Manifest attributes set correctly in jar task
  • copyToLib task configured (if internal plugin)
  • Gradle Version Catalog used for dependencies (if standalone)

Plugin Implementation:

  • Plugin class created with @Plugin annotation
  • Plugin properties defined with @PluginProperty
  • @CompileStatic applied to plugin class
  • Javadoc/Groovydoc comments added
  • Error handling implemented properly
  • Logging added using PluginLogger

Testing:

  • Tests written for plugin functionality
  • Tests written for plugin properties/annotations
  • Tests written for error conditions
  • All tests pass (./gradlew test)
  • Plugin builds successfully (./gradlew build)
  • Plugin jar copied to correct location

Documentation:

  • README documentation created (Howto CLI format)
  • Configuration properties documented in table
  • Usage examples provided
  • Build/Test/Install instructions included

Repository Setup (if standalone repo):

  • Gradle with wrapper
  • Java 17
  • GitHub Actions (build.yml + release.yml)
  • Gradle Version Catalog for dependencies
  • Renovate bot enabled
  • Howto documentation in README

Publishing (if standalone, open source):

  • GitHub secrets configured (PKGCLD_WRITE_TOKEN, SIGNING_KEY_B64, SIGNING_PASSWORD)
  • PKGCLD_REPO_URL org variable set
  • Javadoc fixed (no errors)
  • Release workflow tested
  • PackageCloud publishing verified

Examples

Real-world plugin examples:


Common Mistakes to Avoid

❌ Don't:

  • Forget @Plugin annotation (plugin won't be discovered!)
  • Skip manifest attributes in jar task
  • Forget to copy plugin to plugins directory
  • Use wrong service name (plugin won't appear in UI)
  • Skip tests for plugin properties
  • Hard-code configuration (use @PluginProperty)

✅ Do:

  • Use @Plugin with correct name and service
  • Set all manifest attributes correctly
  • Use Gradle Version Catalog for dependencies
  • Test plugin properties and behavior
  • Document configuration in README
  • Follow Howto CLI conventions for documentation
  • Use @CompileStatic for better performance

Plugin Types Reference

TypeService NameInterfaceUse Case
Workflow StepWorkflowStepStepPluginJob step in workflow
Node StepWorkflowNodeStepNodeStepPluginStep on specific nodes
Resource ModelResourceModelSourceResourceModelSourceNode source provider
NotificationNotificationNotificationPluginJob notifications
Log FilterLogFilterPluginLogFilterPluginProcess log output
Node ExecutorNodeExecutorNodeExecutorExecute commands on nodes
File CopierFileCopierFileCopierCopy files to nodes
StorageStorageConverterStorageConverterStorage backend

Integration with Other Skills

  • create-code: Use for plugin implementation following code standards
  • create-test: Use for comprehensive plugin testing
  • cve-remediation: Check plugin dependencies for CVEs

Resources

© rundeck, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/create-plugin of rundeck/rundeck.

Open the folder on GitHubat commit 9c3c82c

Compare with similar skills

Create Plugin next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Plugin compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Plugin this skillrundeck/rundeck6.3k—~3.6kAutomated safety check: PassApache-2.0
Minecraft Essentials OpsJahrome907/minecraft-agent-skills166—~2.2kAutomated safety check: PassMIT
ReleaseMadAppGang/claude-code284—~1.2kAutomated safety check: PassMIT
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
KubeSphere ServiceMesh Managerkubesphere/kubesphere17k—~2.4kAutomated safety check: PassCustom licence

Similar skills

  • Minecraft Essentials Ops

    Jahrome907/minecraft-agent-skills

    Operate EssentialsX on Minecraft 26.x and 1.21.x servers, including configuration, permissions, economy, kits, warps, homes, and moderation.

    166 GitHub stars~2.2k tokensUpdated 25 days ago
    DevOps & CloudAuto-check passed
  • Release

    MadAppGang/claude-code

    Plugin release process for MAG Claude Plugins marketplace. An agent skill from MadAppGang/claude-code.

    284 GitHub stars~1.2k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed
  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • KubeSphere ServiceMesh Manager

    kubesphere/kubesphere

    Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.

    17k GitHub stars~2.4k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Vercel

    remotion-dev/remotion

    Official

    Set up a Codex monitor for Vercel deployments and preview URLs.

    62k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed

More from rundeck/rundeck

All 10 skills in this repo
  • Backport PR

    rundeck/rundeck

    Backport commits from an existing GitHub Pull Request to a target branch and open a new backport PR.

    6.3k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Cve Remediation

    rundeck/rundeck

    Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.

    6.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Generate standardized CONTEXT.md files for features. An agent skill from rundeck/rundeck.

    6.3k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • I18n Vue Template

    rundeck/rundeck

    Internationalize Vue component templates by replacing all hardcoded strings with $t() calls and adding translations to i18n.ts or enUS.js.

    6.3k GitHub stars~523 tokensUpdated today
    Auto-check: notes
  • Onboard Contributor

    rundeck/rundeck

    Guide a new contributor through the rundeck OSS repo. An agent skill from rundeck/rundeck.

    6.3k GitHub stars~848 tokensUpdated today
    Auto-check passed
  • Write Jest Tests

    rundeck/rundeck

    Write Vue component unit tests. An agent skill from rundeck/rundeck.

    6.3k GitHub stars~486 tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Create Plugin

What does Create Plugin do?

Create bundled Rundeck plugins following development standards. Create Plugin is an agent skill from rundeck/rundeck. Create bundled Rundeck plugins following development standards.

When should I use Create Plugin?

Create Plugin fits situations like: tasks that involve Hooks and plugins; tasks that involve Deployment.

How do I install Create Plugin in Claude Code?

Run `npx skills add rundeck/rundeck --skill create-plugin -a claude-code`. Or copy the skill folder (.claude/skills/create-plugin in rundeck/rundeck) into .claude/skills/create-plugin in your project. Claude Code loads it when a task matches its description.

How do I install Create Plugin in Codex?

Run `npx skills add rundeck/rundeck --skill create-plugin -a codex`. Or copy the skill folder (.claude/skills/create-plugin in rundeck/rundeck) into .agents/skills/create-plugin in your project. Codex loads it when a task matches its description.

Can I use Create Plugin in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rundeck/rundeck --skill create-plugin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-plugin, .gemini/skills/create-plugin, .github/skills/create-plugin and .opencode/skills/create-plugin in your project.

What does Create Plugin need to run?

Going by SKILL.md and its folder, Create Plugin needs credentials named PKGCLD_WRITE_TOKEN, SIGNING_PASSWORD and GITHUB_TOKEN. Our summary lists: A credential in GITHUB_TOKEN; A credential in PKGCLD_WRITE_TOKEN.

Does Create Plugin access the network?

SKILL.md names 6 domains. In commands or code: packagecloud.io; the agent is likely to contact it when it follows the instructions. As links in the text: github.com, pagerduty.atlassian.net, docs.rundeck.com, docs.gradle.org and axion-release-plugin.readthedocs.io. This is read from the text; nothing was executed.

Is Create Plugin safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Plugin use?

Create Plugin is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Plugin use?

About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Plugin?

Skills that share tags, products or a category with Create Plugin: Minecraft Essentials Ops (Jahrome907/minecraft-agent-skills, 166 stars), Release (MadAppGang/claude-code, 284 stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars) and GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Plugin?

rundeck (a GitHub organization) maintains it in rundeck/rundeck, which has 6,329 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 8, 2026.

Source: rundeck/rundeck on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.