Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

my-skill-name

Sterne2

Forks0

Aktualisiert8. April 2026 um 17:52

What this skill does and when Claude should use it. Be specific and slightly "pushy" — Claude tends to undertrigger skills, so include contexts where it should activate even if the user doesn't explicitly ask for it. Example: "Generates changelog entries from git history. Use this whenever the user mentions changelogs, release notes, version bumps, or asks what changed between two commits."

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

script-development

script-development/claude

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	my-skill-name
description	What this skill does and when Claude should use it. Be specific and slightly "pushy" — Claude tends to undertrigger skills, so include contexts where it should activate even if the user doesn't explicitly ask for it. Example: "Generates changelog entries from git history. Use this whenever the user mentions changelogs, release notes, version bumps, or asks what changed between two commits."

My Skill Name

Brief description of what this skill accomplishes and why it exists.

How it works

Instructions

First step
Second step
Third step

Output format

ALWAYS use this structure:
# [Title]
## Section
- Detail

Examples

Example 1: Input: description of what the user asked Output: what the skill should produce

Mehr aus diesem Repository

gleiches Repository

task-writer

script-development/claude

TDD task breakdown and TASKS.md management. Use when planning a new feature, breaking down work into implementation tasks, creating or updating TASKS.md, estimating effort, or organizing multi-step work into phases. Also use when translating a plan document (like docs/plans/*.md) into TASKS.md — includes systematic extraction checklist to ensure nothing is missed. Trigger on: feature breakdown, task planning, "write tasks for", "create TASKS.md", plan-to-tasks conversion, sprint planning, implementation ordering, or when the user mentions wanting to organize implementation steps for a feature.

2026-05-072

kendo-mcp

script-development/claude

MCP integration for kendo project management. Use when creating, updating, moving, or searching issues via MCP tools. Also use when writing user stories, logging time, managing epics, linking branches to issues, or triaging reports (bug reports, feedback). Provides access to projects, issues, lanes, sprints, epics, reports, and teams through MCP resources and tools.

2026-05-052

triage-reports

script-development/claude

Triage incoming reports (bug reports, feedback, feature requests) from the Kendo report queue. Fetches pending reports via MCP, cross-references with existing open issues to find overlaps, then walks the user through each report one-by-one using AskUserQuestion for a verdict: promote to issue, dismiss, or combine with another report. Promoted reports get proper user stories or bug reports following project conventions. Use this skill whenever the user mentions "triage", "triage reports", "check reports", "process feedback", "review reports", "incoming reports", "report queue", "what reports do we have", or any variant of wanting to process the Kendo report queue. Also trigger when the user asks about unprocessed feedback or pending bug reports.

2026-05-052

prepare-issue

script-development/claude

Prepare a kendo issue for development: assign to current user, create a feature branch, link it, move to In Progress, and optionally check out in a worktree with full setup. Usage: /prepare-issue <issue_key_or_id> [N]. Use whenever the user wants to start working on an issue, prepare an issue, pick up an issue, or says "prepare issue", "start issue", "work on issue". Also trigger when combining issue assignment with branch creation, or when the user wants to set up a worktree for an issue.

2026-05-052

catchup

script-development/claude

Load the full context of the current branch and check alignment with the base: git diff summary, commit history, plan/task files, decisions, and (if the project has an issue-tracker skill) the upstream issue details. Reports how far behind the base the branch is and offers to merge on confirmation. Resolves merge conflicts intelligently (auto-resolves obvious ones, asks on ambiguous ones). Use this skill whenever the user wants to understand what the current branch is about, needs context after a /clear, starts a new session, says "what am I working on", "load context", "catch me up", "branch context", "where was I", "summarize this branch", "catchup", "sync my branch", "align with base", "update branch", or any variant of wanting to understand or sync the current state of work. Also use when the user just passes a branch name or issue key and expects you to load its context. Trigger on session start when the branch is not the default branch and the user's first message implies they want to resume work.

2026-05-052

board-sync

script-development/claude

Synchronize the kendo board with GitHub branch and PR status. Use this skill whenever the user wants to check board alignment, sync the board, see what issues are stale, find merged PRs that haven't been moved to Done, or get an overview of branch status for open issues. Trigger on phrases like "sync board", "check board", "board status", "align board", "update board", "which issues are done", or "check branches".

2026-05-052

name	my-skill-name
description	What this skill does and when Claude should use it. Be specific and slightly "pushy" — Claude tends to undertrigger skills, so include contexts where it should activate even if the user doesn't explicitly ask for it. Example: "Generates changelog entries from git history. Use this whenever the user mentions changelogs, release notes, version bumps, or asks what changed between two commits."

My Skill Name

Brief description of what this skill accomplishes and why it exists.

How it works

Instructions

First step
Second step
Third step

Output format

ALWAYS use this structure:
# [Title]
## Section
- Detail

Examples

Example 1: Input: description of what the user asked Output: what the skill should produce