4,935 件 ・ 関連度順
概要と使いどころ
Classify incoming issues into the live GitHub label queue, reproduce where cheap, and write an auditable QUEUE.md snapshot. Use when triaging a backlog, running the scheduled triage routine, or deciding what the factory should pick up next.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an ambiguous factory issue into human-approved product, behavior, design, and implementation slices. Use interactively before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Independently verify a factory pull request, including fail-closed gates, negative test proof, scope, and load-bearing review.
日本語の概要は準備中です。原文の説明を表示しています。
Scheduled health sweep that closes the factory loop - reads CI failures, recent commits, dependency and security advisories, and live queue labels, then files issues and writes an immutable run record. Use for the nightly or weekly monitor routine.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect factory health, stale work, CI, security advisories, and recent run evidence without implementing fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Classify GitHub issues into the factory's live label queue and write an auditable snapshot. Use for backlog triage or a scheduled triage run.
日本語の概要は準備中です。原文の説明を表示しています。
Review factory evidence and propose tighter or looser constraints without editing the charter. Use for a periodic constraint review.
日本語の概要は準備中です。原文の説明を表示しています。
Show the factory control room from live GitHub labels, open PRs, recent run records, gate health, and charter limits.
日本語の概要は準備中です。原文の説明を表示しています。
Simplified Japanese web artifacts builder skill for creating single-file HTML applications with Japanese UI components, i18n settings, and responsive design. Triggers on requests for Webアーティファクト, 単一HTMLファイル, HTMLツール作成, 日本語Webアプリ.
Plan and execute large refactor or rewrite efforts efficiently with parallel multi-agent analysis and implementation. Use when a user asks to refactor many files, split workstreams, analyze a target code area, and coordinate sub-agents with clear ownership and dependency-aware execution.
日本語の概要は準備中です。原文の説明を表示しています。
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
日本語の概要は準備中です。原文の説明を表示しています。
統合リファクタリングエージェント - 既存システムをマイクロサービスアーキテクチャにリファクタリングするための統合分析・設計を実行。/refactor-system [対象パス] で呼び出し。
Plan, verify, and track demo/marketing video production in Busabase — idea to hook/pain-point/storyboard, codebase claim verification, recording progress, post-production handoff, and HyperFrame (Remotion) linkage. Use when the user invokes $kelly-demo-video-factory or /kelly-demo-video-factory, wants to plan a product demo video, write a storyboard, verify a video script's product claims against the codebase, track which shots are recorded, or hand a finished storyboard off to editing/Remotion.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points. This skill covers Duo integration methods, adaptive authentication policies, device trust
日本語の概要は準備中です。原文の説明を表示しています。
Examine Linux system artifacts including auth logs, cron jobs, shell history, and system configuration to uncover evidence of compromise or unauthorized activity.
日本語の概要は準備中です。原文の説明を表示しています。
Code refactoring strategies, technical debt reduction, architecture modernization, and code quality improvement. Use when refactoring code, modernizing legacy code, reducing complexity, or improving maintainability.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guidance for fine-tuning LLMs with LLaMA-Factory - WebUI no-code, 100+ models, 2/3/4/5/6/8-bit QLoRA, multimodal support
日本語の概要は準備中です。原文の説明を表示しています。
Perform 12-Factor App compliance analysis on any codebase. Use when evaluating application architecture, auditing SaaS applications, or reviewing cloud-native applications against the original 12-Factor methodology.
日本語の概要は準備中です。原文の説明を表示しています。
Refactor a whole documentation page in this repository without losing source-verified behavior facts. Use for page rewrites, splits, reorganizations, or substantial shortening of README sections, docs pages, or instruction files. Do not use for ordinary documentation authoring, targeted corrections, or documentation review; use technical-documentation instead.
日本語の概要は準備中です。原文の説明を表示しています。
Debrief a finished Otameshi Tenshoku trial from the employer's side: set the observed facts against the completion criteria agreed before the start, keep expectations added afterwards, second-hand or off-the-job observations and the company's own late or missing support apart, settle the hours actually worked separately from any evaluation, and draft feedback to the candidate that states facts, support gaps and what happens next without promising a hire or continuation the company has not decided. Use when a hiring manager, recruiter or small-business owner wants to review a trial, decide what to tell the candidate, or work out the settlement after a shortfall; do not use to judge the candidate's aptitude or predict a hire, to cut pay or demand unpaid rework because of dissatisfaction, to compare candidates, or to send the feedback, pay, or update records on the user's behalf.
日本語の概要は準備中です。原文の説明を表示しています。
Research a specific company before applying or interviewing by gathering facts from primary and official sources, recording the source and date behind every claim, and keeping anonymous or unverifiable material clearly separated from confirmed fact. Use when a user asks what a company actually does, how it makes money, what its published conditions are, whether a posting matches the company's own disclosures, or what to verify before an interview; do not use to predict hiring outcomes, to repeat review-site content as fact, or to bulk-crawl sites that prohibit automated access.
日本語の概要は準備中です。原文の説明を表示しています。
Review or refactor an existing SKILL.md and its bundled resources — a smaller always-loaded core, conditional references, preserved behavior, lean/guided consumer profiles, and an A/B protocol to compare a candidate with the previous version. Use when a skill repeats itself, loads references on every run, triggers too broadly or misses legitimate requests, or needs its efficiency measured across models. Do NOT use for writing a new skill from scratch, refactoring application code, translating a skill verbatim, or performing the target skill's own task.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Simplify application code for clarity without changing behavior — refactor after tests pass, reduce nesting and duplication, match project conventions. Load when refactoring for readability, cleaning up after a feature ships, or when code review flags complexity. Also triggers on "simplify this code", "code simplification", "make this easier to read", "reduce complexity", "refactor for clarity". Not for compress/split/prune-skill (skill-library files). Pairs with technical-debt-audit.
日本語の概要は準備中です。原文の説明を表示しています。