스킬 찾기

Integrates with Atlassian products to manage project tracking and documentation via MCP protocol, including Jira issue management, Confluence page editing, sprint and backlog management.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an agent or human needs to set up relayfile end-to-end so agents can read and write provider files through a local mount. Covers `relayfile setup`, dynamic integration discovery with `relayfile integration available/search`, Nango and Composio backend selection, Atlassian site selection and metadata, cloud login, OAuth/connect flows, mount verification, `RELAYFILE_LOCAL_DIR` handoff, writeback status and retry commands, and key May 2026 cloud-mount gotchas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Helps a lawyer build and use a personalized Legal Guidance Vault — a local folder of structured, privilege-marked entries capturing legal guidance they've given, searchable later by topic, person, or product. Use this skill when the user says "set up my vault," "archive this meeting/email/thread/doc," "log the guidance I gave on [topic]," "save my notes from [meeting]," "what did I say about [topic]," "find the time I advised [person] on [topic]," or "search my vault for [topic]." Runs a setup interview to learn the user's tool stack (meeting notes, calendar, email, docs, messaging, vault location), then generates a customized vault prompt they can reuse in any future Claude session to start archiving and retrieving guidance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Azure Databricks development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Unity Catalog, Lakehouse/Lakeflow pipelines, AI Runtime/MLflow, model serving, or agents on Databricks, and other Azure Databricks related development tasks. Not for Azure Synapse Analytics (use azure-synapse-analytics), Azure HDInsight (use azure-hdinsight), Azure Machine Learning (use azure-machine-learning), Azure Data Factory (use azure-data-factory).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via MCP server (recommended) or API token authentication (fallback).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagrams and checkable docs from a codebase. Draws ERDs, C4 context/container/component views, API endpoint catalogues, lifecycle/state machines, sequence diagrams, and service-to-service call maps as a validated JSON spec plus a standalone HTML viewer, with Mermaid export. Imports OpenAPI, GraphQL SDL and Prisma; otherwise reads the code (NestJS, TypeORM, Express) and writes the spec. Use for: database diagram, ERD, data model, table relationships, C4 or architecture diagram, system context, API map, endpoint list, "show me the endpoints", status flow, state machine, allowed transitions, "what happens after X is approved", sequence diagram, request flow, how services call each other, microservice map, Mermaid diagram. Also writes documentation as a fact graph: each statement carries its source and a computed confidence, and a drift check fails CI when the code moves. Use to document a system, write architecture or onboarding docs, or explain how a system works.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build managed ingestion pipelines into Databricks using Lakeflow Connect. Use when ingesting from SaaS apps (Salesforce, Workday Reports, ServiceNow, Google Analytics 4, HubSpot, Confluence) or databases (SQL Server cloud and on-prem; PostgreSQL/MySQL CDC in PuPr) into Unity Catalog with serverless pipelines.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze liquid markets with a strict ICT/SMC framework that combines multi-timeframe bias, liquidity sweeps, displacement, close-confirmed MSS/BOS, FVG/OB/Breaker/OTE retracements, premium-discount location, session timing, invalidation, targets, and risk-to-reward. Use for ICT chart reviews, live-market analysis, OHLCV scans, or validating a user's trade thesis. Return an auditable setup status and conditional plan; do not use for generic indicator analysis, order execution, or claims of proven institutional intent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a local file only — use code-overview. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not root-cause a bug to Confluence — use investigate-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it. Use when the user wants a new feature planned, designed, scoped, or specified AND posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not plan to local files only — use plan-a-feature. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features to Confluence — use project-documentation-to-confluence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server. Use when the user wants to post, publish, push, or sync a Markdown file to a Confluence space or page. Requires a configured Atlassian MCP server. Does not write or generate the Markdown itself — point it at an existing file, or use project-documentation-to-confluence for the document-then-publish flow, or plan-a-feature-to-confluence for the plan-then-publish flow. Does not publish to Jira — use work-items-to-jira.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location. Use when the user wants something debugged, diagnosed, or root-caused AND the findings posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not investigate to a local file only — use investigate. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates or updates project documentation for a feature, system, or component and publishes it to a user-specified Confluence location. Use when the user wants feature or system documentation written to Confluence, posted to a Confluence space or page, or synced to a Confluence location. Requires a configured Atlassian MCP server. Does not document to local files only — use project-documentation for that. Does not publish an arbitrary existing markdown file — use markdown-to-confluence for that. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence for that. Does not create architectural decision records — use architectural-decision-record. Does not create coding standards — use coding-standard. Does not produce runbooks — use runbook.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Technical Analysis Agent — price action, indicators, chart patterns, support/resistance, and momentum analysis with Technical Score (0-100)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

0codekit integration. Manage Workspaces. Use when the user wants to interact with 0codekit data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill orchestrates autonomous discovery of brand materials across enterprise platforms (Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, Slack). It should be used when the user asks to "discover brand materials", "find brand documents", "search for brand guidelines", "audit brand content", "what brand materials do we have", "find our style guide", "where are our brand docs", "do we have a style guide", "discover brand voice", "brand content audit", or "find brand assets".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, update, or validate a game brief. Use when the user wants help producing, editing, or validating a game brief before detailed design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Think and work like an expert Cell Biologist. Use when a task calls for Cell Biologist judgment. Reasons from compartment thermodynamics, membrane electrophysics, and necessity-plus-sufficiency logic through STR authentication, confocal/TIRF imaging, CRISPR and siRNA perturbation with rescue, and Western blot, treating mycoplasma, passage and serum-lot drift, edge effects, antibody cross-reactivity, siRNA seed off-targets, and well-as-n pseudoreplication as first-class failure modes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Think and work like an expert Cancer Biologist. Use when a task calls for Cancer Biologist judgment. Reasons from hallmark capabilities, clonal evolution, and TME context; separates driver from passenger, cell-autonomous from stromal mechanisms, and 2D artifacts from PDO/PDX-validated dependencies using TCGA, DepMap, OncoKB, and REMARK-grade biomarker logic.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage knowledge bases and documentation with Confluence Cloud. Use when a user asks to create or manage Confluence spaces, pages, and blogs, build documentation systems, automate page creation from templates, use Confluence REST API v2, manage page trees and hierarchies, set up permissions, integrate Confluence with Jira or other tools, generate reports from Confluence data, build macros or Forge apps, or migrate content between spaces. Covers content management, API automation, templates, and Atlassian ecosystem integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro. Args: [sprint number | dates]. No args = infer the current sprint.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.