200 skills · sorted by relevance
Plan programs that help developers adopt an API or platform. Compare open and curated ecosystems, map the developer journey, and organize documentation, community support, partnerships, and student programs around actual product usage.
Prevent recurring coding-agent mistakes by turning repository evidence into specific instructions, automated checks, regression tests, and failure records. Also checks whether guidance has become outdated and documents changes, verification results, and follow-up work in an adoption report.
Plan enterprise customer onboarding from contract handoff through rollout and continued use. Provides four phases, readiness checklists, ownership checks, and adoption measures to address stalled communication, weak pilot usage, and declining engagement after launch.
Find installable agent skills for a specific task, check their sources and adoption, and present relevant options with explanations, links, and installation commands. Help install a selected skill when the user wants to proceed.
Find installable agent skills for a specific task, check their sources and adoption, and present relevant options with explanations, links, and installation commands. Help install a selected skill when the user wants to proceed.
Evaluate a technology adoption question, a document, or proposed approaches against project evidence and constraints. Receive a supported position with tradeoffs and uncertainty, with an optional panel that consults other models and reconciles their views.
Draft an AI usage policy for a law firm or legal team using published policies and guidance. Adapt selected sections to the organization, cite sources, and flag decisions and open questions for attorney review.
Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use `design-system-governance` (design-systems).
The English summary is being prepared. Showing the original description.
Evaluate Abridge adoption, workflow value, and avoidable operational friction without inventing prices or vendor billing meters. Use when reviewing an Abridge rollout or renewal. Trigger with "analyze Abridge value".
The English summary is being prepared. Showing the original description.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.
The English summary is being prepared. Showing the original description.
Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.
The English summary is being prepared. Showing the original description.
Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or when writing review criteria for the AI era. Produces review guidance: a what-measures-whom analysis, rewritten criteria, calibration rules for mixed-adoption teams, and conversation scripts. For the general review document use performance-review; for redesigning the role itself use role-redesign-for-ai.
The English summary is being prepared. Showing the original description.
Use when answering Scenario admin analytics questions about Creative Unit consumption, most-used models, usage by user or project, AI adoption observability, cached usage data, CSV exports, enterprise PDF reports with charts, or a local analytics dashboard. Keywords: usage API, CU, analytics, adoption, reporting, consumption, cache.
The English summary is being prepared. Showing the original description.
Customer success across onboarding, adoption, retention, and expansion. Use when designing onboarding playbooks, calculating health scores, building QBR decks, planning renewal strategies, or identifying expansion opportunities.
The English summary is being prepared. Showing the original description.
Collaboration platform configuration methodology for legal matter sites. Site architecture, workflow identification, dashboard design, data quality governance, and user adoption for SharePoint, Teams, and equivalent platforms. M365 is the reference implementation — outputs are platform-agnostic enough to brief IT or build simple automations without becoming a Power Automate manual. Use when setting up a matter site, identifying workflows to automate, designing reporting dashboards, managing platform data quality, or driving user adoption. Trigger on: 'set up the matter site', 'configure SharePoint', 'build a dashboard', 'what should we automate', 'brief IT on this workflow', 'nobody is using the platform', 'data quality is poor', 'set up Teams channel', 'matter site structure', 'alerts and notifications', 'user training', 'platform governance', 'status dashboard', 'what workflows can we automate', 'matter site template'.
The English summary is being prepared. Showing the original description.
Applies Geoffrey Moore's chasm-crossing strategy for B2B tech products moving from visionary early adopters to pragmatist mainstream. Use when a product has early traction but stalls before mainstream adoption, when planning a beachhead/niche strategy, when designing whole-product offerings, when positioning against established competitors, or when scaling from innovator usage to industry standard. Triggers include 'stuck between early adopters and mainstream', 'we need a beachhead', 'pragmatist customers won't buy', 'how do we go from 10 to 1000 customers'. NOT for PLG/freemium SaaS (Slack, Notion, Cursor), pure consumer apps, two-sided marketplaces, or AI-native products with bottoms-up viral adoption - their dynamics break the visionary-to-pragmatist sequence.
The English summary is being prepared. Showing the original description.
Investigate MCP tool availability, discovery, and selection, including controlled adoption evaluations.
The English summary is being prepared. Showing the original description.
Use when an instructor asks for a MATLAB Grader assessment setup guide, adoption guide, pilot plan, course-specific rollout, QTI 3 sharing workflow, or recommended MATLAB Grader assessment-item-generation configuration based on a learning objective, course title, course description, module description, lab description, or assessment goal.
The English summary is being prepared. Showing the original description.
Use when an instructor asks for a setup guide, adoption guide, planning guide, implementation checklist, prerequisite check, MATLAB Course Designer course structure plan, Common Cartridge workflow, Simulink starter and solution model planning, LMS import plan, or starter prompt for creating a MATLAB and Simulink enabled course with the matlab-generate-course skill.
The English summary is being prepared. Showing the original description.
Use when an instructor asks for a MATLAB AI tutor setup guide, adoption guide, pilot plan, course-specific rollout, or recommended tutor configuration based on a learning objective, course title, course description, module description, or lab description.
The English summary is being prepared. Showing the original description.
Create adoption strategies and materials to drive design system usage across teams.
The English summary is being prepared. Showing the original description.
Crypto Fundamental Analysis — evaluates project viability, team quality, technology, adoption metrics, and competitive moat with a composite Fundamental Score (0-100)
The English summary is being prepared. Showing the original description.
"Apply the Theory of Planned Behavior to predict behavioral intentions from attitudes, subjective norms, and perceived behavioral control, and identify intervention leverage points. Use this skill when the user needs to predict adoption of a new behavior, diagnose why an intended behavior does not occur, design behavior change campaigns, or when they ask 'why do people not follow through', 'what predicts behavior change', or 'how to increase adoption rates'.".
The English summary is being prepared. Showing the original description.
Use when planning, sequencing, or troubleshooting an org-wide migration from Salesforce Classic to Lightning Experience. Covers the LEX Transition Assistant Readiness Check, asset triage matrix (Visualforce, JavaScript buttons, page layouts, Knowledge, email templates, list views, AppExchange), pilot/wave rollout sequencing, end-user adoption telemetry, and cutover criteria. Triggers: 'lightning experience transition', 'classic to lightning migration plan', 'LEX readiness check', 'why are some users still on Classic', 'turning on Lightning for everyone'. NOT for individual asset migrations like a single VF page (use lwc/visualforce-to-lwc-migration), a single JavaScript button (use admin/custom-button-to-action-migration), or Knowledge article migration (use admin/knowledge-classic-to-lightning) — this skill orchestrates the program. NOT for Lightning App Builder page design (use admin/lightning-app-builder-advanced).
The English summary is being prepared. Showing the original description.