Docs & Writing

paulkinlan Skill

Analyze competing products, tools, or approaches and produce a structured comparison report

siddsachar Skill

Perform multi-source research on a topic and produce a structured report.

siddsachar Skill

Structured workflow for creating professional designs — slide decks, documents, landing pages, app mockups, and motion storyboards.

stefan-stepzero Skill

Visual QA using Playwright as a browser automation library. --setup installs Playwright and creates ui-goals.json; default mode writes inline scripts to navigate, screenshot, and report against goals.

stefan-stepzero Bundle

Review changes across 12 quality dimensions and report findings. Use after a chunk of work or before commit.

faaz17 Bundle

Turn a Markdown report into a clean, branded A4 PDF the president can read or print. Use whenever the user asks for a report/summary/proposal "as a PDF" or "to read properly". Works fully offline on Windows using pandoc + headless Chrome/Edge — no LaTeX or extra installs needed.

faaz17 Bundle

Render the MGT4897 report from Markdown to a submission-ready DOCX and PDF in the Clean Technical Document standard — A4, 1-inch margins, centred black title, dark teal

faaz17 Skill

Report where the VR project stands right now — current phase, what's done, what's blocked, and the literal next action. Use when the user asks "where are we", "what's next", or starts a session cold.

faaz17 Skill

Report where ERC-26 stands right now, including current build phase, what's done, what's blocked, days to the Phase 1 deadline, and the literal next action. Use when the user asks "where are we", "what's next", or starts a session cold.

faaz17 Skill

Report where SumoX-26 stands right now, including current phase, what's done, what's blocked, and the literal next action. Use when the user asks "where are we", "what's next", or starts a session cold.

faaz17 Skill

Report where the internship outreach stands for one or both people — what is sent, awaiting reply, due for follow-up, and the literal next action. Use when starting a session cold, or when asked "where are we" or "what's next".

faaz17 Bundle

Convert Box Notes (.boxnote files) into readable Markdown. Use whenever you need to read, search, or quote the society's meeting notes, calendars, event proposals, or member lists — most of the archive is stored as .boxnote (ProseMirror JSON) which is not human-readable as-is. Also builds a full-text index of the whole archive.

faaz17 Skill

Gate the three ERC-26 Phase 1 deliverables against every stated requirement before the 2026-09-15 submission. Checks the launch contract, package dependencies, clean-container build, the video's six constraints, and the report's six mandated sections. Use in the final week, and before submitting.

faaz17 Bundle

Humanise a finished .docx report end to end - strip machine-generated fingerprints from prose, tables, figures and the OOXML container, then apply the user's house style for headings, tables and captions. Use when asked to humanise, de-AI, clean up or restyle a Word report, dissertation, technical results document or similar deliverable, or when a .docx needs its headings and tables brought into house style. Covers what the generic prose humanizer does not: DOCX container metadata, PNG generator tags, table and figure overflow, blank pages from manual page breaks, and rigorous number-preservation checks.

faaz17 Skill

How to write MBA capstone prose that reads as distinction-level human academic writing — critical rather than descriptive voice, evidence-led paragraph construction, hedging and claim calibration, British English conventions, and the AI-tell patterns that must be edited out. Use when drafting or revising any prose for the proposal or report, and as the style authority before any submission.

faaz17 Skill

How to write the MGT4897 report so it reads as a professional consultant's report to an airport COO while still meeting academic marking standards — the executive voice, analytical rather than descriptive prose, recommendation structure, claim calibration, British English conventions, table and figure discipline, and the AI-tell patterns that must be edited out. Use when drafting or revising any prose, and as the style authority before submission.

faaz17 Skill

Where to find and how to verify data for the MGT4897 DXB report — Dubai Airports newsroom releases, the DWC expansion page, ICAO and IATA statistics, ACI airport rankings and ASQ, UAE government statistics, and the academic journals that carry airport operations and air transport demand research. Includes the source-quality hierarchy, the data-log protocol, and the rules against fabricated figures. Use when sourcing any number, fact, or journal reference.

swm8023 Bundle

在固定的 WheelMaker Wiki Vault 中创建、导入、分类、规范化并发布长期知识。用户要求记录项目知识、导入 Markdown 或 Wiki 材料、整理笔记、维护标签或发布已确认笔记时使用。

khaledsaeed18 Bundle

Turn a rough bug report, idea, or complaint into a well-formed, actionable issue - investigating the codebase first to add reproduction steps, expected vs actual behaviour, suspected location, and acceptance criteria - then filing it with gh or emitting paste-ready markdown. Use when the user says "file an issue for this", "write this up", describes a bug in passing that should be tracked, or wants a feature request made concrete.

khaledsaeed18 Bundle

Vet a candidate name for a software project across package registries, domains, app stores, code hosts, and existing projects, then report which candidate is actually free. Use when picking or clearing a name for a package, library, app, CLI, extension, or repository. For a company or brand name, use business-name-check instead.

khaledsaeed18 Bundle

Vet a candidate business or brand name across domains, social handles, commerce and listing platforms, company registers, and existing businesses, then report which candidate is actually claimable. Use when naming a company, product brand, store, studio, agency, or newsletter. For a package, library, or app name, use project-name-check instead.

byerlikaya Bundle

Keeps documentation in sync with the code: README, usage and related docs when a public API or behavior changes. Leaves no dead or misleading docs behind.

dqtx760 Skill

Generate README, API docs, or user guides for code and projects. Use when writing documentation, creating a README, documenting an API, or explaining how code works for others.

dqtx760 Skill

一站式文章处理：配图(baoyu-article-illustrator) + 封面(article-cover-16x9) + 撰写标题 + 社交媒体改写(x-post) + PPT生成(beautiful-slides)。用户发一篇文章（文件路径或粘贴内容），自动并行完成全部5步。触发词：「处理文章」「一站式」「article pack」「全文处理」「配图封面PPT」「写完帮我全案处理」。

dqtx760 Bundle

从内容到成品PPTX的端到端演示文稿制作，含AI插画生成和18种设计风格。当用户提到"做PPT"、"做幻灯片"、"演示文稿"、"Keynote"、"slides"时使用。

dqtx760 Bundle

数字生命卡兹克（Khazix）的公众号长文写作skill。当用户需要撰写公众号文章、写稿子、续写文章、根据素材产出长文时使用。触发词包括但不限于：写文章、写稿子、帮我写、续写、扩写、公众号文章、长文、出稿、按我的风格写。即使用户只是说"帮我把这个写成文章"或"用我的风格写一下"，只要上下文涉及内容创作和公众号输出，都应该触发。也适用于用户丢过来一个PDF、brief、新闻链接、语音转文字或任何素材说"帮我写篇文章"的场景。不要用于短内容（小红书帖子、推特、朋友圈）或纯标题摘要生成（那个用wechat-title skill）。

dqtx760 Bundle

从文章或一段正文自动生成 16:9 封面图并保存到 D:\data\images\Article-illustrations。用户只要说"生成封面""做个封面""文章封面""博客封面""公众号封面""根据这篇文章出封面""cover image"，或提供文章/Markdown/文本并要求做封面时，就应该使用本 Skill。特别适合中文文章、博客文章、公众号文章、技术文章、观点文章的 1920×1080 横版封面。不要用于文章内多张配图，那种情况用 baoyu-article-illustrator；不要用于卡片海报排版，那种情况用 ljg-card。

dqtx760 Bundle

Create or update content for the agegr/mindmap-ppt static presentation project from a prose draft, article, speech, report, or notes. Use when Codex needs to turn a written document into the project's project/source.js Markdown mind-map data, choose which nodes need illustrations, generate or request GPT Image 2 illustrations matching the project's restrained presentation style, place assets under project/, and validate the result with npm run check.

dqtx760 Skill

使用 NotebookLM 对指定主题进行 Web 深度研究，导出引用文献全文为 Markdown， 并生成中文 3D 风格演示文稿（PPT）到桌面。 触发词：深度研究、Deep Research、notebooklm 研究、研究 PPT、生成研究幻灯片。 用户说"帮我研究 XXX 做个 PPT"、"对 XXX 做深度研究"、"notebooklm 研究一下 XXX"时触发。

mte90 Bundle

Analyze, extract, and migrate Flash/ActionScript game projects (.fla, .swf, .as files) to modern web technologies (JavaScript, TypeScript, HTML5 Canvas, Haxe/OpenFL). Use this skill whenever the user mentions Flash, ActionScript, AS2, AS3, FLA, SWF, decompiling Flash games, extracting assets from Flash files, converting Flash to HTML5, porting Flash games to modern browsers, migrating legacy Flash content, JPEXS, FFDec, Ruffle, CreateJS, OpenFL, Haxe, or any Flash-era game preservation task. Also applies when the user has old .fla or .swf files and wants to understand, extract, rebuild, or modernize their content. NOT for: general web game development without Flash involvement, PDF/document conversion, or video format conversion.

mte90 Skill

Essential rules for code comments, READMEs, and technical documentation.

christopheralphonse Skill

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.

hashintel Skill

Search the live web via Perplexity Search API. Use when you need current documentation, release notes, vendor pages, news, domain-constrained web search, or date/recency filtering. Not for local codebase search or stable docs already in context.

iankiku Skill

(forwward) Structures slide content for pitches, QBRs, board updates, investor updates, strategy decks, and all-hands. Produces slide-by-slide outlines with titles, talking points, and key data per slide — content, not visual design. Use when the user says "help me build a deck", "pitch deck", "QBR", "board update", "what slides do I need", or is preparing a high-stakes presentation without structure yet.

iankiku Skill

(forwward) Writes outcome-first status updates leaders actually read, with options + lean recommendation for blockers. Use when the user says "standup", "status report", "progress update", "weekly update", "executive summary", "update on [project]", or pastes project details without specifying intent. Reads git log, open PRs, tracker state, and the team-memory/ directory. Not for PRDs, postmortems, or peer engineering discussion.

niekcandaele Bundle

Work an entire epic of tickets unattended — for each ticket: plan it, implement it, PR it into an epic branch, drive CI green, merge; then verify the assembled epic once and file follow-ups. Works with any tracker: GitHub, Jira, GitLab, or a markdown checklist. Use when the user hands over a batch of related issues and wants them worked through autonomously ("run this epic", "work through these tickets", "do the whole milestone"). For a single ticket where the work deserves an adversarial implement/review loop, use `player-coach` instead.