Loading...
Loading...
Found 1,285 Skills
Use when bootstrapping skill-loop in a repository, creating a GitHub issue loop starter, or writing and updating skill-loop.yml and starter skills.
Affinity integration. Manage Organizations, Leads, Pipelines, Users, Roles, Filters. Use when the user wants to interact with Affinity data.
Teamwork integration. Manage Organizations, Users. Use when the user wants to interact with Teamwork data.
WeCom meeting management skill, which supports canceling meetings and updating meeting invited members. It is triggered when users need to "cancel a meeting", "delete a meeting", "modify meeting members", "add meeting participants", or "remove meeting members".
Retrieve ALL information from a Jira ticket (description, comments, subtasks, attachments metadata, labels, sprint, status, assignee, reporter, linked issues, custom fields, acceptance criteria) and persist it as a single Markdown file. Use whenever the user says "fetch ticket", "retrieve Jira", "pull ticket info", "get ticket details", "look up ticket", "grab the Jira", "what does ticket X say", "check the ticket", "read the ticket", "show me the ticket", or provides a Jira ticket URL or key like PROJECT-1234. Also triggered by the orchestrating-jira-workflow skill as Phase 1 of the end-to-end pipeline. Trigger even if the user only pastes a ticket key with no other context — that alone means "fetch this ticket." This skill ONLY retrieves — it never modifies the ticket or starts implementation.
Execute a single task from a Jira task plan using a structured pipeline of specialist subagents: planning, testing, refactoring, implementation, documentation, code-quality review, architecture review, security audit, and requirements verification. The user must specify which task number to execute. Use when the user says "execute task 3", "work on task 2", "implement task 1", "start task 5 for PROJECT-1234", or "run task N". Also triggered by the orchestrating-jira-workflow skill as Phase 5 of the end-to-end pipeline (called once per task). Requires that the task plan exists at docs/<TICKET_KEY>-tasks.md. Executes ONLY the specified task — never continues to the next one without explicit user approval.
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
랄프톤 서울 중간발표 양식에 맞춘 slides-grab 기반 인터뷰형 워크플로우입니다. 사용자가 한국어 발표 덱을 원할 때, 필수 인터뷰를 먼저 진행하고 slide-outline.md를 만든 뒤 HTML 슬라이드를 생성·검증하고 viewer를 빌드한 다음 반드시 slides-grab editor까지 실행합니다.
Use Claude Code to simplify the current pull request by safely reducing unnecessary scope, complexity, and noise while preserving the intended outcome.
Complete GitHub pull requests by iterating on CI and review feedback until the PR is ready.
Run Codex code review against the current branch and report only the review comments that are still valid for the current codebase, without applying fixes.
Run Codex, Claude Code, and Gemini CLI reviews against the current branch concurrently, deduplicate the findings, and fix only the review comments that are still valid for the current codebase.