2,719 件 ・ 関連度順
概要と使いどころ
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
日本語の概要は準備中です。原文の説明を表示しています。
Convert human-written CLAUDE.md into AI-native structured-label format. Battle-tested across 4 models. Same rules, fewer tokens, higher compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Design spec with 98 rules for building CLI tools that AI agents can safely use. Covers structured JSON output, error handling, input contracts, safety guardrails, exit codes, and agent self-description.
日本語の概要は準備中です。原文の説明を表示しています。
Critically review a resume/CV against ATS (applicant tracking system) parsing rules, recruiter skim patterns, and keyword alignment with a target job description. Use when the user asks to "review my resume/CV", "check my resume against this job ad", "will this pass ATS", or shares a resume file (.docx/.pdf/.md) for feedback. Provides scored, prioritised, critical feedback — not a rewrite.
日本語の概要は準備中です。原文の説明を表示しています。
Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack. Use this skill whenever working in a project that has oxlint installed (check for `oxlint` in package.json devDependencies or an `.oxlintrc.json` / `oxlint.config.ts` config file). This includes when you need to lint code after making changes, fix linting errors, configure oxlint rules/plugins, set up or modify `.oxlintrc.json`, or migrate from ESLint.
日本語の概要は準備中です。原文の説明を表示しています。
Audit code changes on the current branch and update docs/ + .claude/rules/ to stay in sync. Run before /pr.
日本語の概要は準備中です。原文の説明を表示しています。
Apply frontend code quality rules for React and TypeScript components. Auto-activates when editing component files.
日本語の概要は準備中です。原文の説明を表示しています。
Apply code formatting rules after file edits in the source directory. Use when asked to format code or after making changes to source files.
日本語の概要は準備中です。原文の説明を表示しています。
P0 classification rules for community reports. Six categories that auto-headline regardless of reporter count. Reference doc — invoked by weekly-report when classifying.
日本語の概要は準備中です。原文の説明を表示しています。
TDD Refactor Phase - Improve code while keeping tests green using Simple Design Rules and APP mass
日本語の概要は準備中です。原文の説明を表示しています。
Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"
日本語の概要は準備中です。原文の説明を表示しています。
Read-only reviewer for agent-flow. Judges one diff against the acceptance criteria, AGENTS.md rules, protected paths and risk boundaries; returns a JSON verdict with line-anchored findings. Use when launched with AGENT_FLOW_ROLE=reviewer or asked for an agent-flow review of a diff.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and improves task-specific decision artifacts from application requirements and labeled records. Use for data assembly, primitive and base-model selection, fitting, export/reload, inference policy, or bounded data/model/program improvement. Includes rules and no-training outcomes; does not require a rung ladder or training a general Jev.
日本語の概要は準備中です。原文の説明を表示しています。
Shared setup and rules for the report-skills bundle (report-publisher, client-reporter, proposal-tracker, deck-publisher, report-designer). Loaded by the individual skills for the common ReportRoom MCP publish flow, account bootstrap, and safety gates. Not invoked directly — pick the specific skill for the job.
日本語の概要は準備中です。原文の説明を表示しています。
Validate agent output against declared domain rules and ground truth before trusting it downstream. Trigger after any agent produces output that will be used in a decision, stored persistently, or passed to another agent.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap or harden a project's operating model for mixed human and AI delivery teams. Use when starting a repository, adopting an agent harness, defining authority and risk tiers, coordinating parallel agents safely, binding evidence and review to an exact candidate, or correcting fragmented rules that prevent coherent, consistent, complete delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Sync reusable frontend decisions into persistent project documentation after UI work. Use when frontend changes introduce or modify component APIs, variants, design-system tokens, styling conventions, layout behavior, accessibility rules, interaction patterns, responsive behavior, or agent operating instructions; when the user asks to reflect decisions in components.md, design system docs, AGENTS.md, CLAUDE.md, GEMINI.md, or similar project memory files; or before finalizing frontend work where future consistency depends on decisions made during implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Install or upgrade the event4u agent-config suite. This marketplace plugin is a bootstrap shim — it ships hooks plus this pointer only; ALL skills, rules, and commands are installed via `npx -y @event4u/agent-config init`. Use when the user asks to install, set up, or upgrade agent-config, or wonders why this plugin contains no other skills.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize prediction-pool tips (kicktipp etc.): rules + multi-book consensus odds → expected-points-max answer for every question, scores AND bonus. Triggers 'optimize my pool tips', 'predict'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or editing a rule in src/rules/ — trigger wording, always vs auto classification, size budget — even when the user just says 'add a rule for X'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the rule set is over the Augment budget, when a new rule would breach it, or when asked to audit / merge / prune rules — runs the audit pipeline and proposes a verdict per rule.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and manages project-level overrides for shared skills, rules, and commands — extending or replacing originals from .augment/ with project-specific behavior in agents/overrides/.
日本語の概要は準備中です。原文の説明を表示しています。
Use when running the package's skill linter against all skills and rules to validate frontmatter, required sections, and execution metadata.
日本語の概要は準備中です。原文の説明を表示しています。
When writing validation — Form Requests, rules, custom rule objects, request-boundary design — even when the user just says 'validate this input' or 'check the request' without naming it.
日本語の概要は準備中です。原文の説明を表示しています。