Skill Claude Code
Manage AI agent skills via natural language — install, update, delete, and assign skills to agents using SkillDeck's filesystem conventions.
Skill Claude CodeCodex
Multi-platform, multi-channel notification skill for AI code agents. Sends notifications (sound, macOS alert, Telegram, Email, Slack, Discord, DingTalk) when the agent needs user interaction or completes a task. Supports Claude Code, GitHub Copilot CLI, Cursor, Codex, Aider, and OpenCode.
Skill Claude CodeCodex
Automates the process of creating and setting blog post covers. Reads a markdown file, generates a cover image based on title/subtitle, uploads it, and updates the file's frontmatter (e.g., bannerimg).
Skill Claude CodeCodex
Read from and write to ClipShelf via the clipshelf CLI — query clipboard history, add items, manage tags, and delete entries from the terminal.
Skill Claude CodeCodex
Generates simple gradient-based cover images for blogs or articles with a title and subtitle. Can optionally upload the generated image immediately.
Skill Claude CodeCodex needs its repo
Agent-driven wiki generation workflow for gRPC + Java projects with consistent styling. ⚠️ This skill is optimized for gRPC + Java architecture. It delivers the best results when the project uses gRPC for service communication and Java as the implementation language. For other architectures (REST, GraphQL, non-Java…
Skill Claude CodeCodex
Exports the current AI chat session to a Markdown file. Use this skill when the user wants to export, save, sync, or backup their conversation/chat/session content. Supports both raw export and optional summarization.
Skill Claude CodeCodex
StarRocks upgrade comparison tool. Compares two local branches of a StarRocks repository via commit log diff. Per-commit diff analysis with risk tier classification (HIGH/MEDIUM/LOW/SKIP) for comprehensive impact assessment beyond scanner coverage. 11 compatibility scanners cover config changes, session/system…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: