Loading...
Loading...
Found 743 Skills
Richard Feynman's Integrity Audit applied to any analysis, business plan, or decision. Spawns a team of specialist agents — Source Auditor, Self-Deception Hunter, Translation Tester, Cargo Cult Inspector, Confidence Inverter — who each apply a distinct lens from Feynman's framework to detect dishonesty, self-deception, and cargo cult reasoning. The lead synthesizes into a verdict: is this analysis honest, or is it fooling itself? Use when the user says "feynman this", "integrity audit", "is this honest", "am I fooling myself", "cargo cult check", or wants to stress-test any analysis, plan, or claim before trusting it. Works standalone or as a meta-audit after /munger or /thiel.
Qualtrics XM platform help — CX surveys (NPS/CSAT/CES), Employee Experience (EX) pulse surveys, Strategy & Research, Experience Agents AI, XM Directory, dashboards, REST API v3, MCP servers. Use when surveys aren't getting responses, dashboards won't show the right data, API calls return errors, you're setting up Qualtrics for the first time, confused by XM Directory contact management, need to export response data, comparing Qualtrics vs Medallia, or Qualtrics is too complex and you need guidance. Do NOT use for general NPS/CSAT strategy across tools (use /sales-customer-feedback) or product review collection like Trustpilot or G2 (use /sales-customer-reviews).
Customer feedback, NPS, CSAT, CES, Voice of Customer strategy across platforms — survey design, response rate optimization, closed-loop feedback, text analytics, benchmarking, program governance. Use when NPS scores are stagnant, survey response rates are low, feedback isn't driving action, unsure which CX metric to use, need to design a VoC program, comparing feedback tools (Medallia vs Qualtrics vs SurveyMonkey vs Typeform), or customers feel over-surveyed. Do NOT use for product review collection like Trustpilot or G2 (use /sales-customer-reviews) or in-app message surveys (use /sales-in-app-messaging).
StartuPage platform help — startup ecosystem combining Stripe/LemonSqueezy/Polar/RevenueCat/Dodo-verified MRR leaderboard, founder + startup sub-page profiles, and a four-track Opportunities marketplace (hiring, fundraising Open Rounds, co-founder matching, startup acquisitions). Free plan with 2 themes and the StartuPage badge, Starter $5/mo (1 opportunity, custom domain, badge removal, 8 themes), Growth $9/mo (3 opportunities, pro analytics), Lifetime $179. Use when setting up a founder profile and choosing whether to show exact MRR / a range / private, connecting a payment provider for verified revenue, picking a pricing plan or the Lifetime Pass, posting a hiring / fundraising / co-founder / acquisition opportunity, comparing StartuPage vs TrustMRR / Indie Hackers / Peerlist / Wellfound, or climbing the Top Startups or Top Founders leaderboard. Do NOT use for cross-marketplace side-project valuation (use /sales-side-project-valuation).
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "I can't understand what this test is doing", "tests pass but bugs still reach production", "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
Develop Xiaohongshu note ideas and drafts from rough thoughts, lived experience, or existing source material. Use this when the user has a scattered idea, a half-formed opinion, a working draft, or a professional insight and wants help shaping it into a Xiaohongshu note with stronger structure, trust, readability, and platform spread potential. This skill is especially for professional, experience-dense, memo-style notes that should feel like a real operator sharing judgments, not a generic content writer producing polished fluff.
Maintain the LovStudio website's partners section AND align partner logo rows on event posters / hero strips: scrape brand logos from homepages, normalize to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets cropped), strip embedded background rects from icon-style SVGs, composite icon + wordmark when only an icon is available (using brand fonts), wrap logos in a fixed-size grid box (96×30 with subtle border) for stable matrix layouts, replace existing logos with user-provided files, append new partners to the PARTNERS array with i18n taglines across zh-CN/en/ja/th, and audit the section for dead URLs / missing files / missing translations. Also handles cross-asset visual height parity (multi-logo strips on dark backgrounds, "logo 不等高", unified-color filter recipe). Trigger when the user mentions "合作伙伴", "partners", "trusted by", "新增 logo", "标准化 logo", "替换 logo", "审计合作伙伴", "维护合作伙伴", "logo 不一样高", "logo 对齐", "logo 大小不一致", "logo 颜色不统一", "logo 不清晰", "logo 糊了", "矩阵格子", "等宽 box", "图标加文字", "compose wordmark".
You are a **Developer Advocate**, the trusted engineer who lives at the intersection of product, community, and code. You champion developers by making platforms easier to use, creating content tha...
Expert Kuaishou marketing strategist specializing in short-video content for China's lower-tier city markets, live commerce operations, community trust building, and grassroots audience growth on 快手.
Conversion-focused design that removes friction and guides users toward action through clarity, trust, and speed.
Build a compilable type-level skeleton from a high-level architecture spec before writing any implementation logic. Use when you have an architectural assessment, design doc, or restructuring plan and need to prove the new architecture is sound before migrating code. Also use when asked to "scaffold the new architecture", "create type stubs", "build the shell", "flesh out this spec", "skeleton the modules", or any request to turn architectural intent into verified structure. This skill follows the "Human Builds the Shell" paradigm: types are hard constraints that the compiler enforces, so if the skeleton compiles, the architecture is structurally sound. Especially valuable for large refactors where you don't trust agents to maintain coherence.
[Hyper] Update semantic versions across node/rust/python projects, keep discovered version files synchronized, and prefer the installed `git-commit` skill for the final git step with a direct fallback when it is unavailable.