Manage brand tone/style for all writing skills
日本語の概要は準備中です。原文の説明を表示しています。
4.3万 件 ・ 関連度順
概要と使いどころ
Manage brand tone/style for all writing skills
日本語の概要は準備中です。原文の説明を表示しています。
Complete B2B sales system — from ICP to closed-won. Discovery frameworks, objection handling, pipeline management, forecasting, and deal acceleration. Works for any B2B company.
日本語の概要は準備中です。原文の説明を表示しています。
Design irresistible offer packages with real salary benchmarks, negotiation playbooks, and competitive counter-strategies. Co-designed with Siku (司库). Includes total compensation calculator, negotiation scripts, and BATNA analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Audit wiki health — "wiki health check", "audit the wiki", "find contradictions", weekly pass, before a major content release. Catches contradictions, stale pages, orphans, duplicate concepts and broken links.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim L3 pack. Bundles: HIPAA + ISO 13485 + ISO 14971 + FHIR/HL7. Primary framework: ISO 14971 (medical-device risk management).
日本語の概要は準備中です。原文の説明を表示しています。
Maxim e-commerce direct-response video — engineered for PURCHASE. The primary sales style. Uses AIDA + JTBD + Loss Aversion + Scarcity + Anchoring stacked for maximum conversion. Every second is behavioral leverage.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim L2 pack. Bundles: All six L1 packs. Primary framework: Behavioral Moat Framing Doctrine (ADR-007).
日本語の概要は準備中です。原文の説明を表示しています。
Maxim motion-comic narrative video — engineered for narrative engagement and origin-story investment. Uses Sequential Art Closure + Narrative Transportation + Curiosity Gap Theory to turn brand origins and episodic content into deeply-engaging narratives that viewers finish and share.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and track delivery — plan, sprint, project, timeline, milestone, task breakdown, backlog, Kanban, RACI, changelog governance. The COO office's workflow coordination domain.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim Master Design Intelligence — full-spectrum UI/UX orchestration. Activates all design sub-domain skills in parallel. Use when a task spans multiple design domains simultaneously: product design strategy, interaction design, information architecture, usability heuristics, design critique, cross-platform consistency, design leadership. The master conductor of all Maxim design agents.
日本語の概要は準備中です。原文の説明を表示しています。
Ingest raw sources into the structured wiki — "ingest", "add this to my wiki", new files in raw/, clippings, sources, ideas, nightly ingest. Produces pages with YAML frontmatter and a mandatory Counter-Arguments section.
日本語の概要は準備中です。原文の説明を表示しています。
Test and assure quality — test plan, QA, coverage, unit test, integration test, end-to-end, performance, benchmark, regression. Applies TDD and FIRST principles for the CTO office's tester.
日本語の概要は準備中です。原文の説明を表示しています。
Security review and threat work — threat modeling, vulnerability assessment, penetration test, incident response, OWASP Top 10, LLM Top 10, API Top 10, CVE triage, STRIDE, NIST CSF, SBOM. Auto-loops on any task touching PII, auth, payments or regulated data.
日本語の概要は準備中です。原文の説明を表示しています。
Automate browser interactions, test web pages and work with Playwright tests.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a whole spec by orchestrating subagents over its ticket graph; auto-detects the most recent task folder when no argument is given.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks to test, verify, interact with, or automate web pages and browsers. Trigger for requests involving Chrome automation, browser testing, web scraping, screenshot capture, element selection, or checking web applications. Also trigger when user mentions "browser tools" explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when creating, modifying, or managing Claude Code plugins and plugin marketplaces. Trigger when working with plugin manifests (plugin.json, marketplace.json), creating plugin directory structures, adding plugin components (commands, skills, agents, hooks), version bumping, or when discussing plugin development workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.
日本語の概要は準備中です。原文の説明を表示しています。
PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS).
日本語の概要は準備中です。原文の説明を表示しています。
Manages Obsidian Daily Notes via the official Obsidian CLI. Creates and opens daily notes, appends entries (journals, logs, tasks, links), reads daily notes and vault files, searches vault content, and handles relative dates like "yesterday", "last Friday", and "3 days ago". Requires Obsidian 1.12+ with Command line interface enabled.
日本語の概要は準備中です。原文の説明を表示しています。
Plain-English translation layer for non-technical Copilot CLI users. Translates every approval prompt, error message, and technical output into clear, jargon-free English with color-coded risk indicators.
日本語の概要は準備中です。原文の説明を表示しています。
All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.
日本語の概要は準備中です。原文の説明を表示しています。