研究与知识

Summarize weekly GitHub contributions for writing weekly reports

zc277584121

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.

zc277584121

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.

crm-data-governance

Design and operate CRM field-level governance - who owns each CRM field, which system is authoritative for it, how often it must be refreshed, and how the rules are enforced. Produces a field dictionary, per-field ownership, a system-of-record map with write-precedence and conflict rules, freshness SLAs, an enforcement plan, a field lifecycle, and a governance cadence. Use whenever the user mentions field ownership, single source of truth, system of record per field, data dictionary, stale CRM data, custom field sprawl, "which system wins", or "our CRM fields contradict each other" - even if they never say "governance". Covers B2B and B2C. Do NOT use for org-wide, object-level source-of-truth policy - use mbfinotti/revops-skills@revenue-data-governance-strategy instead.

paid-media-scaling

Decide when a proven paid campaign has earned a budget increase, how large each step should be, how the ramp sequences over weeks and months, and how to avoid performance collapse on the way up - including readiness gates, vertical vs horizontal scaling, and rollback triggers. Use whenever the user asks whether to scale a campaign, how fast ad spend can rise, mentions a budget ramp, a scaling ceiling, or says performance collapsed after the budget was raised - even if they never say 'scaling'. Covers B2B and B2C. Do NOT use to split a fixed total across campaigns (mbfinotti/advertising-skills@ad-spend-allocation) or to track daily spend against a set budget (mbfinotti/advertising-skills@ad-budget-pacing).

ad-negative-keywords

Build and maintain negative keyword lists from search term reports to cut wasted ad spend in paid search - n-gram query mining to surface irrelevant search terms, the right negative match types and exclusion levels (account, shared list, campaign, ad group), and a review cadence that avoids overblocking queries that convert. Use whenever the user mentions a search term or search query report, irrelevant clicks, junk traffic, wasted ad spend, or wants to exclude or block keywords - even if they never say 'negative keywords'. Covers B2B lead gen and B2C/e-commerce; needs the account's query data. Do NOT use for account-wide underperformance with no query-level evidence - use mbfinotti/advertising-skills@ad-account-diagnostic instead.

ad-budget-pacing

Track daily and weekly spend against a single campaign or account budget and flag under-pacing or over-pacing before it hurts results, reporting the pacing ratio, projected period spend, and the corrective daily spend behind every alert. Use whenever the user mentions budget pacing, spend tracking, burn rate, spend vs budget, projected month-end spend, underspending or overspending, or asks whether a campaign is on pace - even if they never say 'pacing'. Covers any ad platform, B2B and B2C, calendar-month or fixed-date flights. It flags and recommends; it never changes budgets or bids. Do NOT use to plan a scale-up (mbfinotti/advertising-skills@paid-media-scaling) or to set CAC/ROAS thresholds (mbfinotti/advertising-skills@ad-spend-guardrails).

advertising-kickoff

Before starting any paid advertising work, before each recurring advertising review, and whenever routing is unclear, route the task to the right skill of the advertising-skills collection - or say plainly that none fits - and bootstrap or resume the project's shared context artifact. Use at every advertising project start, on later sessions of the same project to re-route without re-interviewing, and whenever the user mentions a new ad campaign or paid media project, asks which advertising skill they need, or wants a periodic advertising check-in - even if they name no skill at all. Prefer this whenever several skills could apply, since the collection has three colliding clusters - the hirer-vs-candidate pair, the budget cluster, the creative cluster - and it returns a short-list plus an ordered skill chain rather than a single guess. Do NOT use when the task already maps cleanly to one skill, such as a pure account audit - that is mbfinotti/advertising-skills@ad-account-diagnostic.

ad-audience-targeting

Turn a business's ICP and buying signals into a layered ad audience targeting plan - cold/broad prospecting, interest and in-market behavioural segments, lookalike/similar, first-party lists, and retargeting pools - each sized against platform audience floors, budgeted to the learning threshold, and kept from overlapping by exclusion rules. Use whenever the user mentions ad targeting, who to target with ads, audience tiers or layers, broad vs. layered targeting, audience overlap between campaigns, or mapping an ICP onto ad audiences - even if they never say 'audience'. Covers B2B and B2C. Do NOT use to pick the seed customers behind a lookalike (mbfinotti/advertising-skills@lookalike-audience-seeds) or to sequence retargeting messages (mbfinotti/advertising-skills@retargeting-funnel).

ad-buyer-group-mapper

Map the likely buying committee for an offer, deal size, and industry, and give each role a messaging angle plus the ad-targeting proxy - job function and seniority, account list, account-level intent - that actually reaches them, sequenced by buying stage. Use whenever the user mentions a buying committee or buying group, decision makers, influencers or blockers, who signs off, targeting the economic buyer or a champion, per-role ad messaging, or whether one broad message beats per-role targeting - even if they never say 'buying committee'. Covers B2B committees and multi-decider household purchases. Do NOT use to size or build the audiences themselves - use mbfinotti/advertising-skills@ad-audience-targeting instead.