1.4천건 · 관련도순
DEPRECATED — superseded by tree-sitting. This skill generated persistent _MAP.md files; tree-sitting does the same AST extraction at runtime (~700ms for 250 files) with no artifact to write, commit, or keep in sync. Use tree-sitting for "map this codebase", "explore repo", "understand structure", or any code navigation task. The final working version is archived at release mapping-codebases-v0.8.0.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, planning usability tests, or validating designs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Counts and compares blog posts across a target and competitors, audits content freshness via sitemap lastmod dates, and maps competitor organic keywords (US, non-branded, informational) against the target to surface ranking gaps. Use when asked to compare blog counts, content volume, publishing cadence, content freshness, keyword mapping, keyword gap analysis, or competitor keyword reports — e.g. "how many blog posts does X have vs Y", "how fresh is content on X", "where does [target] rank for [competitor] keywords", "keyword gap between X and Y". Works from company names alone. Always use for blog comparison, freshness audits, and keyword mapping tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research, expand, and cluster keywords for content strategy. Use when planning content topics, building keyword lists, expanding seed keywords, clustering by topic and intent, or mapping keywords to funnel stages. Triggers on "keyword research," "keyword expansion," "keyword clustering," "content topics," "what to write about," "topic ideation," "content planning," "6 circles method," "seed keywords," "keyword difficulty," "search volume," "intent mapping," "pillar content strategy," or "content calendar planning." For SEO optimization and auditing, see seo-and-aeo-strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a learning progression showing prerequisite-to-mastery steps for a target skill or understanding. Use when sequencing content, designing diagnostics, or mapping prerequisite gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tags harness-decomposed curriculum items (KUDs, LTs, criteria) with a school's developmental band metadata while preserving source voice and labels. Supply the band schema; the skill derives mapping rules from it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Data governance strategy, quality validation rules, and data dictionary management for vehicle insurance platform. Use when defining data quality standards, implementing validation rules, managing field mappings, resolving data conflicts, or establishing data governance processes. Covers data cleaning standards, quality metrics, and mapping management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dasel v3 query patterns for Hibernate .hbm.xml mapping files — entity-table binding, Java property-to-column extraction, one-to-many set/list/bag relationship tracing, many-to-one foreign key discovery, batch scanning across 60+ HBM files. Use when querying Hibernate ORM class mappings, extracting schema metadata from Java persistence layer, or auditing entity-column relationships in enterprise legacy codebases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maps your company's GTM motion (PLG, SLG, or Hybrid) to concrete funnel stages with inputs, outputs, and qualification criteria per stage. Detects motion type from website + Exa research, then produces pre-close + post-close stage definitions, the FETE mapping (Fit / Engagement / Tier / Eligibility), and closed-lost re-entry paths. Triggers - "funnel strategy", "funnel stages", "pipeline stages", "sales process", "lead qualification", "GTM motion mapping", or any work defining how leads flow through the business. Upstream - recommended company-context, icp-research. Downstream - feeds lifecycle-marketing, outreach-emails, content-strategy. NOT for lead scoring logic (use /lead-scoring) or lifecycle email campaigns (use /lifecycle-marketing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building or refining an Ideal Customer Profile (ICP), defining target personas, mapping buyer psychographics, or discovering where prospects gather online. Triggers: 'build my ICP', 'define target customer', 'who should I sell to', 'refine ICP', 'persona mapping'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Develops PE sector theses with industry mapping, secular trends, fragmentation opportunity, and target universe identification. Use when building sector strategies, mapping investment themes, or identifying subsector opportunities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Redact rendered visual artifacts — Mermaid diagrams, SVGs, and HTML dashboards — before public disclosure, using an ordered longest-first mapping table (specific label, then namespace label, then catch-all placeholder) that swaps sensitive identifiers for descriptive stand-ins while preserving structure, node ids, and teaching value. Covers whole-word identifier replacement, node-label-vs-node-id discrimination, re-rendering the derived image from the redacted source, and verifying the result through the redaction gate. Use when a diagram or dashboard built from internal findings must ship to a public mirror without leaking the names behind it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
매핑 에디터. proposal_script.md와 generate_제안서.py 간의 매핑을 검증하고 수정합니다. 스크립트의 레이아웃 지시가 코드에 올바르게 반영되었는지 확인. 트리거: /mapping-editor, 매핑 검증, 스크립트-코드 매핑
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
STIX 2.1 bundle creation reference. Object types, relationships, and JSON templates for structured threat intelligence sharing. Includes the per-claim mapping of evidence grades (access level and claim support) from /quality-of-information-check to STIX confidence, and the reverse mapping on import.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to answer "which attacker techniques do our controls actually stop, and how well?", "what controls should I have for this threat?", or "what telemetry should I collect to detect it?" — joining a customer's or your own security control baseline to ATT&CK techniques using a public, versioned evidence base of 9,545 control-to-technique mappings from six sources. Produces four ranked lists (addressed strongly, addressed weakly, real gaps, and techniques no control anywhere addresses). Use for control gap analysis, security programme prioritisation, board reporting on coverage, or the Resistance Strength side of a FAIR risk assessment. Invoke after /threat-actor-profiling or /lookup-liberty91 has produced a technique list.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
White-box source code security review structured around OWASP ASVS 5.0 (427 verification requirements across 16 chapters). Reads and understands application source code to build a security-aware knowledge base that enriches all downstream skills. Covers: tech stack identification, route/endpoint mapping, authentication and authorization architecture, dangerous function patterns, source-to-sink data flow tracing, IaC review, dependency analysis, ASVS compliance mapping, and LLM integration security (prompt injection, tool abuse, output handling, RAG poisoning, MCP server patterns). When LLM/AI framework usage is detected, automatically reviews OWASP LLM Top 10 patterns from source code and chains into /ai-redteam with white-box context for live endpoint testing. Chains into /pentester, /threat-modeling, /web-exploit, /api-security, /cloud-security, /analyze-cve, /credential-audit, and /ai-redteam — providing white-box context that transforms black-box testing into targeted, informed assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes remote access trojan command-and-control by mapping the RAT command set, identifying the C2 transport and beacon parameters, and cataloging operator capabilities from static strings and config. Activates for requests to analyze RAT C2, map a trojan command handler, or identify remote-access capabilities and C2 transport.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Surface and visualize hidden dependencies blocking delivery. Use when the user says "map our dependencies", "what's blocking what", "dependency audit", "why are teams blocked", "we have a bottleneck", "draw out the dependencies", or asks to identify cross-team blockers - even if they don't explicitly say "dependency mapping". Based on "Making Work Visible" by Dominica DeGrandis (time theft, invisible work, flow blockers).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Annotate genetic variants (GWAS hits, eQTLs, rare variants) with ENCODE functional data to interpret non-coding variation. Use when the user has variants of interest and wants to understand their regulatory context, identify causal variants from GWAS loci, assess variant impact on regulatory elements, perform enrichment testing of variant sets in tissue-specific annotations, or link variants to target genes through enhancer-gene maps. Handles the full post-GWAS workflow from variant set → tissue mapping → functional annotation → fine-mapping awareness → enrichment → variant-to-gene → prioritization. Use this skill for ANY variant interpretation task involving ENCODE chromatin, accessibility, TF binding, or 3D genome data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when gathering, structuring, and documenting requirements for a Financial Services Cloud (FSC) wealth management implementation — including financial planning workflow discovery, portfolio review process mapping, client lifecycle requirements, advisor tooling needs, and FSC architecture determination (managed package vs. FSC Core). Trigger keywords: wealth management requirements, FSC requirements gathering, financial planning workflow, portfolio review process, advisor tools setup, FSC data model scoping, wealth management process mapping. NOT for implementation, configuration, or code — use financial-account-setup, fsc-action-plans, or apex/fsc-financial-calculations for those. NOT for FSC architecture decisions — use architect/wealth-management-architecture. NOT for Health Cloud or NPSP requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to configure a Lightning Service Console app in Salesforce — Console Navigation (split view), workspace tabs and subtabs, the utility bar with Omni-Channel, Macros and History, Quick Text, keyboard shortcuts, and navigation rules per object. Trigger keywords: Service Console, console app, workspace tabs, subtabs, utility bar macros, Omni-Channel utility, split view, Quick Text, console navigation rules, keyboard shortcuts service console, navType Console, workspaceConfig mappings, WorkspaceMapping fieldName, UtilityBar FlexiPage, tabLimitConfig, listPlacement, MacroInstruction, QuickText Channel multipicklist, isNavTabPersistenceDisabled. NOT for opening or refreshing console tabs from code — use lwc/lwc-console-workspace-api. NOT for Omni-Channel routing setup — use admin/omni-channel-routing-setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Salesforce-anchored personas and journey maps where every persona ties to a Permission Set Group, primary record types, list views, dashboards, automation, and a measured mobile/desktop posture, and journeys walk each task end-to-end with friction tags that drive UX decisions. NOT for stakeholder authority / RACI (use admin/stakeholder-raci-for-sf-projects), NOT for system-side process flows (use admin/process-flow-as-is-to-be), NOT for Lightning page design itself (use admin/lightning-app-builder-advanced or the lightning-record-page-auditor agent), NOT for pure design / UX research disconnected from org artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when picklist data quality has degraded: unrestricted picklists accepting garbage API values, dependent picklist relationships bypassed by integrations, record type picklist value mappings drifting out of sync, or orphaned values appearing in reports. NOT for the value-deactivation runbook or the API-name-vs-label trap — use admin/picklist-data-integrity. NOT for initial picklist creation or Global Value Set design — use admin/picklist-and-value-sets. NOT for record type configuration itself — use admin/record-types-and-page-layouts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when designing lead nurture journeys in MCAE (Account Engagement / Pardot) Engagement Studio — mapping content to funnel stages (Awareness, Consideration, Decision), behavioral trigger rules, branching program paths, and MQL handoff criteria to Sales. NOT for building a journey in Marketing Cloud Journey Builder — use admin/journey-builder-administration. NOT for the scoring and grading model behind MQL — use admin/mcae-lead-scoring-and-grading.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.