Docs & Writing

aiunlocked1412 Bundle

สร้าง test case ครอบคลุม edge case พร้อม bug report template และ regression checklist

nvidia-omniverse Skill

Adding new tested code snippets for documentation pages. Use when adding code examples to RST docs, creating new doc pages, or migrating inline code blocks to tested snippets.

haomingz Bundle

Create and edit Word documents (.docx) — C# + OpenXML SDK for creation, WIR engine for editing/comments/tracked changes. Use for any .docx task including document creation, editing, comments, revisions, footnotes, TOC, and Markdown-to-Word conversion.

haomingz Bundle

按 CVPR、ICCV、NeurIPS、ICML、ACL、ICLR 等顶级会议惯例撰写、排版与呈现科研论文的结构化指南。覆盖全流程：分章节起草、图表设计、LaTeX 排版、叙事逻辑与投稿前打磨。适用于撰写、修改或将手稿排版成 camera-ready 或预印本 PDF。

haomingz Bundle

Utilizes a suite of tools to facilitate exhaustive, evidence-based deep research and long-form report engineering. Enforces a minimum 10-iteration search cycle, recursive reflection, and the production of structured reports exceeding 10,000 words with mandatory IPython visualizations and specific paragraph logic.

haomingz Bundle

创建结构清晰、文字为主的投资分析备忘录，输出为 DOCX 或 PDF 文件。支持两种经典格式：风投式交易备忘录（问题/方案/市场结构）和主题/宏观备忘录（叙事性文章风格），适用于撰写投资论点、交易备忘录、合伙人信函或投委会材料，并进行深入的私募、风投或公开市场分析。当用户提及“投资备忘录”、“交易备忘录”、“投委会材料”、“写一下对[公司/主题]的分析”或“起草一份投资论点”时触发。

haomingz Bundle

创建专业精美的投资路演PPT和商业计划书，风格参照中国创业公司融资路演材料，默认输出18页、白色背景搭配藏青色点缀的PPTX格式，也可导出PDF，支持中英文内容。当用户需要为投资人制作路演PPT、撰写商业计划书或融资方案、生成包含市场分析和财务预测的公司概览幻灯片，或提及创业融资/投资备忘录演示文稿时触发。

haomingz Bundle

生成具有顶级咨询公司视觉风格的数据驱动市场洞察报告，内容涵盖高管摘要、趋势分析和战略建议，输出为PDF、DOCX或PPTX格式。当用户需要创建、撰写或制作市场研究报告、行业分析报告、消费者行为报告、竞争格局分析、市场趋势报告、战略洞察报告、行业白皮书或购物者报告时触发。

haomingz Bundle

创建震撼的地理杂志风格演示文稿（PPTX），具备编辑级版式、大幅主图、数据驱动图表与奢华美学。适用于地点合集、奢侈房产展示、旅行目的地演讲、地图主题策展、建筑作品集等，带杂志风格的网格概览与章节分隔页。

haomingz Bundle

财报三表（利润表、资产负债表、现金流量表）深度解读，自动进行同比/环比变动分析并执行多维度财务异常检测（如应收账款暴增、经营现金流与净利润背离、存货积压及毛利率突变等）。当用户需要解读财报、分析三表、做同比/环比比较、检测财务异常信号、评估现金流质量或计算关键财务比率时触发，关键词包括财报、三表、同比、环比、异常检测、应收账款、现金流背离、毛利率、financial statements、earnings report。

haomingz Bundle

生成专业的一级市场/风险投资（PE/VC）行业研究报告，覆盖TMT、消费、医疗健康、工业等常见赛道，输出深度讨论型（15-25页）或传统行业型（30-60页）的PDF、DOCX或PPTX文档。当用户要求创建行业研究报告、赛道深度研究、市场分析报告、投资备忘录、Best Ideas摘要，或请求分析特定行业、市场趋势、竞争格局及技术图谱时触发。

haomingz Bundle

生成国泰海通/海通国际风格的证券研究报告。适用于个股研究、行业跟踪、投资简报等金融文档。触发词：国泰海通、海通国际、行业跟踪、股票研究、证券研究。支持国内与国际双模板。

haomingz Bundle

创建机构级别的投资研报，采用卖方研究视觉风格、信息密集型版面与完整章节结构。适用于股票、固定收益、策略、行业、衍生品、ETF 或量化研究。对标高盛、摩根士丹利、摩根大通等投行研报风格，带封面页、编号图表、术语表与披露声明。支持 PDF、DOCX、PPTX 多种输出。

haomingz Bundle

撰写遵循卖方券商惯例的大宗商品专业研究报告与投资建议，涵盖能源、金属及农产品，输出机构级的展望报告、交易建议、主题投资演示或研究报告，支持PDF、DOCX和PPTX格式。当用户请求撰写大宗商品市场展望、构建交易建议、制作研究报告，或提及大宗商品价格预测、供需分析、宏观投资主题等关键词时触发。

uphiago Skill

Hunting skill for xxe vulnerabilities. Built from 10 public bug bounty reports including SVG-upload XXE, Office-doc (PPTX/DOCX) XXE, SOAP XXE, SAML AssertionConsumer XXE, blind OOB XXE via DTD callback, parameter-entity XXE, XXE-to-LFI, XXE-to-SSRF, and XXE-to-RCE chains (Adobe Commerce CosmicSting CVE-2024-34102). Use when hunting XXE on any target — emphasis on OOB-Or-It-Didn't-Happen Gate for blind cases.

uphiago Skill

Hunt server-side template injection (SSTI) across Jinja2 (Flask/Django), Twig (Symfony), Freemarker (Java), ERB (Rails), Spring, Velocity, Mako, Thymeleaf, Smarty. Detection probes use double-curly and dollar-curly math expressions evaluated server-side. Once an engine is fingerprinted, escalate to RCE via the engine-specific class-walker, callback-registrar, or Execute-utility patterns documented in disclosed reports. Detection patterns: error messages reveal engine, blank or numeric eval reveals expression mode. Targets: email templates, PDF/report generators, CMS preview features, error pages with user input. Use when hunting RCE via template rendering, when content shows engine fingerprints, when finding endpoints that compose strings with user input before render.

uphiago Skill

Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi — report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula, impact statement formula, severity decision guide, downgrade counters, pre-submit checklist. Use after validating a finding and before submitting. Never use "could potentially" — prove it or don't report.

uphiago Skill

Evidence-capture and PoC-redaction discipline for bug-bounty submissions: cookie redaction protocol (which fields to mask, Preview annotation / Burp panel hiding / DevTools workflow), PII black-bar discipline (what to mask in other-user data — names, emails, phones, faces — vs what is safe to leave — usernames, trace IDs, request bodies), HAR file sanitization (jq filters for Cookie/Set-Cookie/Authorization headers), Burp Repeater/Intruder screenshot hygiene (hide request body, show only Results table for rate-limit attacks), Chrome DevTools Console PoC patterns (credentials include so cookies are not echoed, labeled console.log), screenshot capture order, filename conventions, post-submission rotation hygiene. Use BEFORE any PoC screenshot, BEFORE attaching a HAR, or whenever preparing evidence with session cookies or other-user PII. Pairs with bugcrowd-reporting and report-writing.

uphiago Skill

Finding validation before writing any report — 7-Question Gate (all 7 questions), 4 pre-submission gates, always-rejected list, conditionally valid with chain table, CVSS 3.1 quick reference, severity decision guide, report title formula, 60-second pre-submit checklist. Use BEFORE writing any report. One wrong answer = kill the finding and move on. Saves N/A ratio.

uphiago Skill

Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints, debug-info framing, user-enumeration with sensitive PII, theoretical-issue counter), chained-finding cross-reference patterns, target selection for QA-vs-prod programs, researcher-side hygiene (Bugcrowdninja email alias, account state restoration, friendly-tester posture). Use when filing a Bugcrowd submission, when VRT default seems wrong, when triager closes as OOS or downgrades severity, when chaining linked submissions, or when scope distinguishes production from QA. Pairs with report-writing and triage-validation.

uphiago Skill

Client-facing red-team deliverable format — codifies the Subject / Observations / Description / Impact / Recommendation / PoC structure used for external red-team engagements (not bug-bounty platform reports). Different audience, different tone, different cadence. Built from an authorized engagement deliverable where 14 findings were packaged into a 52KB MD + 2.2MB DOCX with 16 embedded screenshots. Use when the engagement is "external red team for an enterprise client" (not H1/Bugcrowd/Intigriti), when generating the final report, when the client has specified a custom report format, or when packaging findings into DOCX/PDF.

build-with-dhiraj Bundle

Multi-source research with citations and structured reports. Triggers on "deep research", "research report".

build-with-dhiraj Skill

Validate a product/startup idea via Reddit, X/Product Hunt, and WebSearch. Produces a 9-section report. Triggers on "I have an idea", "validate this", "market for X".

build-with-dhiraj Bundle

Closed-loop reasoning discipline distilled from Claude Fable 5's handover manual — read the request beneath its words, decompose by checkability, verify by re-derivation, label known vs guessed, prosecute your own conclusion, report answer-first with tripwires. Use for any task where being wrong is costly - debugging, root-cause analysis, incident investigation, code review verdicts, architecture or migration decisions, data analysis, quantitative claims, estimates, or anything irreversible or outward-facing (deletes, sends, publishes, money). Trigger whenever the user asks for a verdict, diagnosis, or recommendation, says "think carefully", "are you sure", "double-check", "be rigorous", "think like fable", or "fable mode" — and even unprompted, before delivering any confident conclusion that rests on unverified claims.

gianlucanaarden Skill

Past Nassim Taleb's Antifragile framework toe op elk plan, businessmodel, beslissing of strategie. Classificeert elk onderdeel als Fragiel, Robuust of Antifragiel. Zoekt asymmetrische downside (fragiliteit), enkele faalpunten en hidden risks, en wijst op optionality, convexiteit en asymmetrische upside (antifragiliteit). Genereert concrete acties via barbell strategie, via negativa, optionality stacking en skin-in-the-game. Gebruik deze skill ALTIJD wanneer iemand zegt "antifragiel", "antifragile", "Taleb", "Black Swan", "convex denken", "optionality", "barbell strategie", "via negativa", "Lindy effect", "skin in the game", "ik wil bestand zijn tegen schokken", "wat als de markt klapt", "hoe maak ik mijn bedrijf onverwoestbaar", "single point of failure", "wat is mijn grootste risico", "hoe profiteer ik van chaos", "hoe word ik sterker van volatility", "stress test mijn plan", "mijn omzet zit te veel op één klant", "ik ben afhankelijk van één kanaal", of wanneer iemand een plan heeft dat goed werkt in stabiel

xspoonai Bundle

AI-powered API documentation generation tool that auto-generates comprehensive API docs from source code, including OpenAPI/Swagger specs, Postman collections, and markdown documentation with examples and authentication details.

spike-faye-lei Skill

Per-page Codex review + targeted python-pptx / Beamer fixes for academic talk slides. Use AFTER /paper-slides (or any externally generated PPTX/Beamer) when the deck looks 'mostly OK' but the user wants a final pass that aligns visual weight with a reference, bumps PPTX fonts to projector-readable size, kills italic style leaks, fixes text-frame overflow, and catches per-slide layout drift. Trigger phrases: "polish slides", "slides 排版不对", "PPTX 字体太小", "和 Beamer 比一下", "per-page review", "和 codex 一页一页过".

spike-faye-lei Skill

Generate conference presentation slides (beamer LaTeX → PDF + editable PPTX) from a compiled paper, with speaker notes and full talk script. Use when user says "做PPT", "做幻灯片", "make slides", "conference talk", "presentation slides", "生成slides", "写演讲稿", or wants beamer slides for a conference talk.

spike-faye-lei Skill

Scan the full wiki to detect health issues and produce a tiered fix-recommendation report (covers all entity types in runtime/schema/entities.yaml + graph consistency)

spike-faye-lei Bundle

Ingest a paper into the wiki — creates pages (papers + concepts + methods + people) and builds all cross-references and graph edges. Trigger whenever the user says "ingest", "add this paper", drops a `.pdf` / `.tex` / arXiv URL, or asks to fold a paper into the knowledge base.

spike-faye-lei Bundle

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations, with color palettes of UPerform company; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," "幻灯片," "PPT," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

spike-faye-lei Skill

Two-thread adversarial review: a fresh reviewer constructs the strongest 200-word rejection memo, then a second fresh reviewer defends the paper point-by-point and surfaces still-unresolved critical issues. Use when user says "kill argument", "adversarial review", "hostile review", "rebuttal preparation", "reviewer-2 simulation", or before submitting a theory paper that has already passed standard review rounds.

h-mmer Skill

Generate submission-ready reports for all confirmed findings. Runs dedup, PoC builder, quality check, and report writer. Usage: /report bounty or /report pentest

h-mmer Skill

Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.

h-mmer Skill

Report Writing

h-mmer Skill

Score a report draft before submission. Usage: /quality <draft-path-or-finding-description>