3.6천건 · 관련도순
Update CRM opportunity fields such as stage, close date, amount, and next steps. See the exact before-and-after values, apply only requested or accepted changes, and verify the saved record through a link.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create unit test scaffolds, sample data, and mocks from code or specifications. Analyze coverage reports to prioritize missing tests, and guide test-driven development through failing tests, minimal implementation, and refactoring.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare nine methods for setting priorities, including RICE and ICE, which score ideas using factors such as impact and confidence. Use formulas, selection guidance, and linked templates to choose an approach for customer problems, initiatives, or requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or improve unit tests for Apache ShardingSphere classes. Cover the target class’s behavior and affected branches, verify explicitly requested coverage goals, and consolidate suitable scenarios into parameterized tests, which run the same checks with different inputs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find community skills related to a recent task and the user’s legal practice area. Suggest only strong matches that are not already installed, mention each skill once, and leave installation to a separate command.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Provide language-specific reference files for test analysis skills. The catalog helps agents recognize test methods, assertions, skipped tests, waiting patterns, setup and cleanup hooks, external dependencies, and tagging capabilities across different frameworks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit Reddit Ads data to assess community targeting, creative fit, and bidding efficiency. Get prioritized fixes, suggested communities to add or exclude, and feedback on whether ad copy suits the communities it reaches.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a BB plugin for the Community marketplace by checking its release source, assembling metadata, an overview and images, validating the submission, and opening a pull request for review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check whether the MCP connection responds by sending a message and receiving it unchanged, or getting 'pong' when no message is supplied. Useful for CLI health checks, basic SignalR connection tests, and round-trip timing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn raw test results into readable reports with pass and fail totals, unstable tests, and coverage, meaning how much code tests exercise. Package results for releases, quality assurance, or reviews, with follow-up actions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when the user asks to "plan the participation ramp before we promote", "how much account history or karma do we need in this community", or "design entry incentives and member lifecycle for our own Discord"; produces the per-community pre-promotion warming plan — account-history/tenure expectations (Estimated, named sources), a give-before-ask ledger spec, a per-community etiquette + rule digest with last-verified dates, and the warming → active graduation criteria that channel-registry requires as state-transition evidence — plus the owned-community variant (entry paths + member lifecycle for your own Discord/Slack/forum/企业微信私域). Not for launch-day submissions or T-0 threads — use community-launch-runner. 社区预热/先给后取/账号养成/毕业标准
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a fair, enforceable community moderation policy. Use when standing up or overhauling moderation for a forum, Discord, Slack, subreddit, or any user community. Produces a clear code of conduct with examples, a graduated enforcement ladder tied to specific triggers, an appeals process, moderator guidelines, and the handling for the severe cases (threats, doxxing, brigading) that need immediate action. Governs member conduct in a user community — distinct from [[community-management-playbook]], which manages a brand's own social-media channels (comments, DMs, tone, response templates).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work <work-unit>. Uses get_work_unit, list_tasks, update_task, get_work_unit_progress.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unit economics analysis for China-focused portfolio companies. Adapted from the original unit-economics skill for Chinese business models, pricing, and market dynamics. Triggers on "A股单位经济模型", "单元经济模型", "unit economics China", "unit economics [company]", "LTV/CAC China", or "Cohort analysis [company]".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Read this catalog to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md for pytest/unittest, typescript.md for Jest/Vitest/Mocha, java.md for JUnit/TestNG, etc.). Do not invoke this reference-only skill — its bundled files are read by the quality agent and analysis skills needing framework-specific lookup tables (test markers, assertion APIs, skip annotations, sleep patterns, mystery guest indicators, integration markers, setup/teardown, tag-support capability).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in Directory.Build.props; EnableMSTestRunner, EnableNUnitRunner, UseMicrosoftTestingPlatformRunner, or YTest.MTP.XUnit2; .NET 10 global.json test.runner and TestingPlatformDotnetTestSupport; translating VSTest filters, logger, coverage, blame, or dump arguments; replacing VSTest@3; and exit code 8 or zero tests. Also use for xUnit v3 MTP filters during a v2-to-v3 upgrade. Do not use for framework conversion, TFM, UWP, or WinUI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Quarkus project; Reduce slow @QuarkusTest usage with Mockito-first tests; Add @InjectSpy partial mocking or QuarkusTestProfile configuration in Quarkus tests; Convert repeated test methods to @ParameterizedTest with @CsvSource or @MethodSource; Write fast pure unit tests for Quarkus services. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to find Slack groups, Discord servers, Reddit communities, forums, or online communities where their target audience hangs out. Also use when the user mentions "where to promote", "find communities", "community marketing", or "distribution channels".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode tests", "test this feature", "write integration tests", "make sure this doesn't break", "add test coverage", "TDD this feature", or any task involving test creation, test-driven development, or quality assurance. Maps Given/When/Then scenarios directly to test methods using NUnit assertions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
UniTask async/await patterns for Unity including cancellation, lifecycle binding, and coroutine interop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unity 6 core concepts and architecture guide. Use when working with GameObjects, Components, Transforms, Scenes, Prefabs, ScriptableObjects, or Unity project structure. Covers the entity-component architecture, object hierarchy, tags, layers, and project conventions. Based on Unity 6.3 LTS documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unity 6 multiplayer and networking guide. Use when building multiplayer games, working with Netcode for GameObjects, NetworkManager, NetworkObject, NetworkBehaviour, RPCs (ServerRpc, ClientRpc), NetworkVariables, or Unity multiplayer services (Relay, Lobby). Covers client-server architecture, state synchronization, and scene management. Based on Unity 6.3 LTS documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.