Research &amp; Knowledge

fusion-research

Source-backed research orchestrator for the Fusion ecosystem. Routes to the correct research agent based on question type. Returns source-backed evidence only; will not invent Framework behavior, component APIs, skill catalog relationships, platform guidance, or backend implementation details. USE FOR: any research question needing source-backed evidence about Fusion Framework APIs, EDS components, the Fusion skill catalog, Fusion platform documentation, or backend service implementation. DO NOT USE FOR: implementing code changes, installing or editing skills, MCP setup or troubleshooting, or inventing Fusion behavior without evidence.

equinor

prismic

Use whenever Prismic is mentioned or relevant in any way — including questions, lookups, configuration, repository settings, content modeling, content types, slices, localization, previews, API tokens, webhooks, syncing local models, or reading Prismic documentation. Load on any reference to Prismic, even for simple questions.

prismicio

partnerships-kickoff

Before starting any partnerships work - and before routing to any other skill in the mbfinotti/partnerships-skills collection - run this router first. It matches the task (channel, alliance, co-sell, marketplace, affiliate, influencer, or referral) to exactly one sibling skill, says plainly when none fits, and bootstraps or resumes the project's shared partnerships-context.md artifact so the next session starts warm instead of cold. Use whenever the user opens a partnerships project, asks which partnerships skill they need, resumes partner work after a gap, runs a periodic partner, affiliate or influencer check-in, or describes a partner, creator or commission problem without naming a skill - even if they never say kickoff, routing or partnerships, and even when they name a downstream task directly. Routing and shared context only - it never does a sibling skill's work itself, and always emits the full owner/repo@skill target it routes to.

partner-economics

Model the unit economics of one partner relationship - partner P&L, margin modeling, cost-to-serve, referral-fee and lifetime-value split, channel partner ROI, partner CAC vs direct CAC, ramp and payback - to decide whether to sign, scale, renegotiate, or exit that partner. Covers B2B channel and alliance partners plus B2C affiliate and creator economics. Use whenever the user mentions partnership unit economics, a single-partner business case, reseller, VAR, MSP, OEM or marketplace deal economics, revenue-share and margin-stack analysis, or asks whether a partner is worth pursuing, even if they never say economics. Do NOT use for ranking a portfolio of candidates - use mbfinotti/partnerships-skills@alliance-prioritization instead.

partner-enablement

Sequence the training, content, and certification a B2B partner program needs to make partners self-sufficient sellers - the partner enablement roadmap, not the training content itself. Covers the skills-gap needs assessment, enablement tracks split by partner role and type, certification design and refresh cadence, and a pilot cohort, all designed backwards from the partner's first deal. Also covers B2C analogs (franchise, dealer, ambassador education). Use whenever the user mentions partner enablement, partner certification, channel partner training, a partner onboarding curriculum, or ramping partners to a first deal, even if they never say enablement. Do NOT use for affiliate welcome emails - use mbfinotti/partnerships-skills@affiliate-onboarding-sequence instead.

extension-object-storage

General file/object storage, such as for images, videos, files, documents and other bulk data. Perfect fit for image galleries, video galleries, and other file or object management. Supports large files beyond IC limit, with browser-cached HTTP URL access.

caffeinelabs

screenshot-compression

Compress PNG and JPEG screenshots in place using pngquant and jpegoptim, keeping the original format for maximum compatibility.

github-traffic

Fetch, store, and visualize GitHub repository traffic data (views, clones, referrers, stars) with trend charts. Requires repo push access.

git-summarize-weekly

Summarize weekly GitHub contributions for writing weekly reports

perpetuum

Set up, supervise, and control a persistent multi-layer "explore → execute → escalate" agent loop on a project. Use whenever a user asks to keep an agent running on a task across sessions or days — finding bugs, polishing writing, distilling a style, watching feeds, scanning for gaps, or any task whose value grows with how many findings the agent produces. Also use when the user wants to inspect, pause, resume, stop, or send a new instruction to an already-running perpetuum task.

mintlify

Comprehensive reference for building Mintlify documentation sites. Use when creating pages, configuring docs.json, adding components, setting up navigation, or working with API references. Routes to detailed reference files for all components and configuration options.

codewithshreyans

make-documentation

Use when writing READMEs, architecture, changelogs, release notes, runbooks, notebook docs, install docs, or security articles; produces docs. Do not trigger for API docs, AGENTS.md, or diagrams.

callicrate

agents-md

Use when the requested deliverable includes creating, reviewing, moving, splitting, or updating a repository AGENTS.md; produces scoped repo guidance. Do not trigger for standalone skills, prompts, non-AGENTS instruction files, READMEs, changelogs, or architecture docs.

callicrate

artist-workspace

How to work in artist directories. Use when adding or updating artist context (identity, brand, voice, audience), adding songs, organizing files inside an artist directory, or figuring out where something belongs. Also use when the user mentions an artist by name and the task involves their files, context, or content — even if they don't say "artist directory." This includes tasks like researching an artist, creating content for an artist, updating an artist's brand, or adding a face guide.

recoupable

synap

Add persistent, structured long-term memory to AI agents using Maximem Synap. Use this skill whenever the user is building, debugging, or evaluating an AI agent and mentions any of: "memory", "long-term memory", "persistent memory", "agent memory", "remember across sessions", "context window", "agent forgets", "user preferences", "personalization", "RAG over conversations", "multi-tenant memory", "memory layer", "Mem0", "Zep", "Letta", "SuperMemory", "Cognee", or asks how to integrate memory into LangChain, LangGraph, LlamaIndex, OpenAI Agents SDK, Pydantic AI, CrewAI, AutoGen, Google ADK, Haystack, Agno, Semantic Kernel, Microsoft Agent Framework, NVIDIA NeMo, LiveKit, Pipecat, Claude Agent SDK, Mastra, Vercel AI SDK, or MCP (no-code). Also trigger on direct mentions of "Synap", "Maximem", "maximem-synap", or `synap-*` package names. Covers SDK setup, scoping (User/Customer/Client), ingestion, retrieval, and one drop-in package per framework.

vaibhav0806

sales-kickoff

Before starting any sales project, and before answering a sales request that spans more than one sales topic or names no skill at all, run this router first. It routes the task to exactly one skill in the sales-skills collection, or says plainly that none fits, and bootstraps or resumes the project's shared sales-context.md artifact, producing a short-list plus an ordered skill chain. Fires on the state of the conversation rather than the subject matter, at a sales project start, at a periodic sales check-in or recurring sales review, on a mid-project re-route, or on any broad or ambiguous sales request such as "which sales skill do I need" or "where do I start with sales". Covers both altitudes, CRO-altitude planning (motion, ICP, market sizing, segmentation, tiering, org structure, quota, coverage, comp) and execution (outbound, cold calling, discovery, objections, MEDDPICC, recaps, call review, hiring, career). Run it even when sibling skills are already in daily use elsewhere.

sales-career

Coach one person through landing and growing a sales career - SDR/BDR entry, SDR-to-AE promotion, and beyond - across B2B SaaS and commission-heavy B2C (real estate, insurance, solar, auto). Covers sales interview prep (mock cold call, sell-me-this-pen, candidate-authored 30-60-90 plan), quantified track-record evidence, sales skill-gap roadmaps, employer diligence, and sales offer evaluation from the candidate's seat, anchored to dated benchmarks (Bridge Group, RepVue, NAR). Use for "sales career", "break into tech sales", "sdr interview prep", "sdr to ae path", "evaluate this sales offer". Does not cover the hiring side (mbfinotti/sales-skills@sales-hiring), job searching or auto-applying, resume file generation, or deal execution tactics.

sales-market-sizing

Estimates TAM, SAM, and SOM for a market or sub-segment to ground sales capacity, territory, and quota planning - top-down, bottom-up on named accounts or population math, value theory, triangulation, a capacity-based SOM ceiling, and a per-layer refresh cadence. A macro planning exercise for sales leadership and RevOps, covering B2B and B2C. Use whenever the user mentions TAM, SAM, SOM, market size, addressable market, "how big is this market", or the number behind next year's quota, even without those acronyms. Sizes for planning, not pitching. Do NOT use for defining the ICP (mbfinotti/sales-skills@sales-icp-definition) or turning SOM into quotas (mbfinotti/sales-skills@sales-quota-setting).

sales-discovery-questions

Builds a sequenced sales discovery question set - pain, root cause, impact, urgency - for a specific deal or persona, sized to the call length, with follow-up ladders, branch triggers, and a do-not-ask list. Covers B2B (SDR qualification through multi-stakeholder AE discovery) and high-ticket B2C consultations. Use whenever the user mentions discovery call prep, qualification questions, SPIN or pain-funnel questions, a first-meeting agenda, or "what should I ask this prospect", even without the word discovery. Do NOT use for rebuttals (mbfinotti/sales-skills@sales-objection-handling), the cold-call opening (mbfinotti/sales-skills@cold-call-opener), or grading a finished call (mbfinotti/sales-skills@sales-call-review).

deal-value-calc

Builds the ROI and business case for one deal - value drivers, full investment, ROI, payback, three cases conservative-first, and a one-page case the champion can forward. The buyer supplies every assumption, each number labeled buyer-supplied, benchmark, or rep-assumed, and none invented. Covers B2B and high-ticket B2C. Use whenever the user mentions ROI, business case, payback period, TCO, cost of doing nothing, "justify the price", or CFO sign-off, even without the word value. Do NOT use for price rebuttals (mbfinotti/sales-skills@sales-objection-handling) or discount trade planning (mbfinotti/sales-skills@negotiation-concession-planner).

deal-champion-mapping

Builds an evidence-graded stakeholder map for one active deal from titles, call notes, email and meeting activity, and CRM contact roles, naming the likely champion, economic buyer, and blockers, each with a confidence level tied to observed behaviour rather than title. Covers B2B buying committees and high-consideration B2C households. Use whenever the user mentions a champion, economic buyer, power map, deal org chart, multi-threading, single-threaded risk, or "who actually decides", even without the word stakeholder. Do NOT use for qualification scoring (mbfinotti/sales-skills@meddpicc-scorecard) or scanning notes for general risk (mbfinotti/sales-skills@deal-red-flags).

sales-meeting-recap

Turns raw sales call notes into a structured recap email with agreed next steps - every action item carrying an owner, a date, and a deliverable - plus mutual close plan (mutual action plan) items when the deal warrants one. Restates the buyer's pain in their own words and never invents a commitment the notes don't contain. Covers complex B2B committee deals and transactional or B2C motions. Use whenever the user mentions a recap email, follow-up after a sales call, next steps email, post-call summary, or a mutual action plan, even without the word recap. Do NOT use for judging how the call went (mbfinotti/sales-skills@sales-call-review).

revops-kickoff

Before starting any RevOps or Sales Ops task, and at the start of every session on an ongoing RevOps project, run this first - it routes the task to exactly one skill of the revops-skills collection or says plainly that none fits, and bootstraps or resumes the project's shared, versioned context artifact so the next session starts warm instead of cold, ending in a short-list plus an ordered skill chain. Run it even when the collection's other skills are already used daily - a new project is a new context. Also use whenever the user mentions a revops kickoff, a new RevOps project, a revops project start, revops or crm skill routing, a periodic RevOps check-in, a recurring RevOps review, "which revops skill do I need", or "where do I start with RevOps" - even if they never name a skill, and even if the request looks like it already belongs to one specific skill. Do NOT use for routing quota-carrying sales tasks - use mbfinotti/sales-skills@sales-kickoff instead.