Docs & Writing

kangwang42 Bundle

中英文学术与研究报告文本的证据约束编辑及终审技能。用于已有论文、学位论文、摘要、研究或分析报告、基金申请书、cover letter、 response to reviewers、rebuttal、编辑部往来和科研邮件的局部内容修订、授权范围内改写、压缩、语气校准或终审。 先锁定研究事实、数据、统计量、引文、结论边界、允许修改范围和用户纠正，再检查内容功能、论证结构、段落节奏、因果与论断强度、术语一致性及学术书面语。论文从零写作或全文/章节级结构性重写转 academic-publishing； 实际 Word 编辑再配合 docx。不得生成研究发现，不得改动数据或引文，不用于规避披露要求或优化 AI 检测分数。

kangwang42 Bundle

基于已验证的代码、结果数字唯一来源和表图生成或结构性重写中英文期刊论文、学位论文部件、摘要、题名、cover letter、审稿回复、highlights 和投稿正式往来，并完成正式投稿或返修提交前确认。开工先用 biostat-principles；完整稿或论文级结构性重写同时用 evidence-research 核验证据与报告要求，终审用 academic-humanizer；实际 Word 操作再配合 docx。研究生学位论文开题报告使用 graduate-opening-report；已有文本的局部润色或压缩只用 academic-humanizer。

kangwang42 Bundle

以期刊同行评审人身份审查生物医学、临床、公共卫生、流行病学与生物统计稿件，建立稿件内数据和论断证据链，区分报告缺项与方法缺陷，评价研究设计、偏倚、统计、结果解释、透明度、语言和伦理，并生成可定位、分级、可行动的完整审稿报告。用于用户明确要求同行评审、审稿、评审稿件、major/minor comments、reviewer report 或投稿评议。开工先用 biostat-principles；需核验文献或方法依据时用 evidence-research；Word/PDF 文件操作加 docx/pdf，最终措辞可用 academic-humanizer。论文总结、文献综述、作者侧润色或改稿、response to reviewers、投稿前项目审计分别转相应 skill，不用于替编辑作最终录用决定或在无原始数据时声称验证数据真实性。

kangwang42 Bundle

生成、结构化重写和终审研究生学位论文开题报告，覆盖中文正文、学院表单、技术路线、研究计划、参考文献与归档前一致性检查。用户要求撰写硕士或博士开题报告、依据学院模板或既有范本生成开题材料、把研究想法整理成可评审的开题报告时使用；实际 Word 读写加 `docx`，PDF 范本读取加 `pdf`，流行病学或生物统计研究设计加 `biostat-principles` 与 `epi-study-design`。不用于完整学位论文、仅局部语言润色或只改 Word 版式。

kastalien-research Skill

Generate a status report across all workstreams using git history and GitHub issues. Shows active work, recent changes, and open PRs.

kastalien-research Bundle

Effect-TS expert — write, debug, refactor, and explain code using the Effect ecosystem (effect, @effect/platform, @effect/rpc, @effect/cli, @effect/schema, @effect/cluster). Use this skill whenever the user works with Effect-TS code, mentions Effect services/layers/fibers/streams/schedules, asks about Effect error handling or dependency injection, wants to migrate code to Effect, or asks questions like 'how do I do X in Effect'. Also trigger when you see Effect imports in code being discussed, or when the user mentions Effect patterns like generators, pipe, Context.Tag, Layer.provide, or Schema.Class. This skill has a semantic search index over the full Effect documentation — use it to ground answers in official docs rather than guessing.

kastalien-research Skill

Capture learnings from the workflow into reusable documentation. Stage 7 of the development workflow.

seasonedcc Bundle

Write human-facing prose for this repository in our voice — the README, every page under docs/, and any other copy a person reads. Use when writing or editing documentation, GitHub-facing text, or prose in release notes meant for human readers.

seasonedcc Skill

Install, configure, upgrade, and repair the seasoned-skills workflow package — the source of this project's generated doctrine, skills, and runtime code. Use when installing or upgrading the workflow, changing seasoned-skills.config.ts, running or debugging the sync, reading a failed-sync report, or wiring a new machine.

viewway Skill

````markdown

warpdotdev Bundle

Generate a reviewable changelog draft from PRs merged in a release range. Extracts explicit CHANGELOG markers, classifies unmarked PRs, adds external contributor attribution, and outputs markdown + JSON artifacts. Does NOT mutate channel_versions.json.

borkweb 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.

harshanandak Bundle

Report where the project stands and what work is in flight -- the Forge status snapshot. Reach for this at session start or whenever the user says "/status", "where am I", "what's in progress", "catch me up", "resume work", or "what changed recently". It surfaces the workflow stage, your active/claimed issues, all issues ranked by composite score with conflict-risk flags, stale already-merged issues (which it closes), and recent commits. Use it to ORIENT and decide the next move -- it reports state; it does not plan, develop, or claim issues. Not for: routing to a stage skill or documenting the full issue-verb surface (kernel); ranking and EXPLAINING a single next-ready or blocked issue to hand off (triage-ready); everyday create/update/list/close/comment/search issue ops (issue-basics); the Hermes harness's token-bounded orient/recap contract (hermes-forge); or the post-merge CI health check that closes issues after a merge lands (verify).

harshanandak Bundle

Runs the Forge verify stage — the post-merge health check performed AFTER a PR is merged: switch to master and pull, confirm the merge landed, check CI is green on master, confirm deployments are up, remove the merged worktree, safe-delete the branch, and close the kernel issues the PR resolved. Use when asked to verify a merge went cleanly, confirm post-merge CI health on master, check deployments after merging, clean up a merged branch or worktree, or close the issue now that its PR is merged — and whenever `/verify` is invoked. Strictly the POST-merge stage: use shepherd instead to monitor a still-open PR toward merge, review to fix and resolve PR feedback before merge, ship to push the branch and open the PR, rollback to undo an already-shipped change, status to merely report the current stage without acting, and issue-basics to close an issue unrelated to a just-merged PR.

harshanandak Bundle

Hermes⇄Forge boundary: Hermes CONSUMES Forge state, never a second source of truth. Use whenever a Hermes session runs on a Forge repo: at session start, before acting on an issue, or when you need CURRENT state. Read state ONLY via `forge orient` / `forge recap <issue-id>` (bounded JSON envelope), citing each source's `path`/`authority`; never reconstruct it from raw stores or kernel internals. Writeback ONLY via `forge comment`/`update`/`create`; NEVER leak Hermes profile or session memory into Forge state. Triggers: "orient me / current project state", "where did this fact come from, cite it", "orient came back truncated", "persist a decision into Forge", "safe to store in kernel state?". NOT the Forge session router over stage skills (kernel), NOT the human "what stage am I in" report (status), NOT everyday issue create/update/close/search CRUD (issue-basics), NOT ranking the next ready issue (triage-ready), NOT live PR monitoring (shepherd—outside Hermes, unseen by orient).

warpdotdev Skill

How and when to log (log::* levels, safe_* macros) and report errors to Sentry (report_error!) in the Warp codebase. Use when adding or reviewing any logging or error reporting — picking a log level, deciding log vs. report_error!, keeping sensitive data out of logs, or surfacing an error to Sentry.

warpdotdev Skill

GUI desktop app only. Repo-specific bug reproduction guidance for Warp. Specializes the core reproduce-bug-report skill for logged-out Warp UI repros, exact reporter-version installs, and login-free onboarding.

a-v-ershov Skill

Produce a project's initial documentation end to end, from a raw idea to a buildable spec. Use when starting a new project or a major new initiative and you want the full guided flow rather than running each step by hand. Orchestrates gather-context, validate-idea, define-product-requirements, create-user-flows, define-design-decisions, design-architecture, define-code-style and design-dev-architecture — each phase researching real-world facts within a fixed budget, running an adversarial review whose findings it applies in place, and emitting a research doc plus a short human summary. Works on an empty repo or one that already has code.

build-with-dhiraj Bundle

Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any Langfuse feature works. This skill covers CLI-based API access (via npx) and multiple documentation retrieval methods.

fabioc-aloha Skill

Improves documentation accuracy, discoverability, consistency, and Markdown quality while deferring to repository conventions.

fabioc-aloha Skill

Generates a current skill-inventory report from the live Scout host. Use when a user asks to list skills, inventory skills, or report the current ACT skill library.

jsuvic Skill

Use to run a bounded documentation drift scan, update, and re-verify loop that stops when docs match the code, on no diff, or on a repeated identical mismatch.

qa-aman Skill

Update user personas from new feedback, pilot data, or research. Use this skill when: - New pilot data or feedback reveals changed user behaviors or pain points - Annual persona review is due (1-2x per year) - New user segments are discovered that need persona documentation - Existing personas need validation against recent data

kyrie66nb Skill

Compile LaTeX paper to PDF, fix errors, and verify output. Use when user says "编译论文", "compile paper", "build PDF", "生成PDF", or wants to compile LaTeX into a submission-ready PDF.

ramboz Bundle

Inventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.

ramboz Bundle

Drive the red-green-refactor loop for any non-trivial code change. Auto-detect the project's test runner (pytest / vitest / jest / node --test), invoke it via the `tdd.py` helper, and act on the normalized exit code. Use when you write a test, TDD this feature, let me test-drive a behaviour, are about to implement [feature], want to run my tests, ask is my coverage complete, or ask are tests green. Do not use for one-off exploratory scripts, throwaway spikes, or pure-documentation edits that touch no executable code.

ramboz Bundle

Verify a finished slice is actually ready to land (tests green, DoD ticked, deviation log present, STATUS=DONE) and emit a deterministic landing checklist for either direct merge-to-main or PR-shaped integration. Use when the user says "land this slice", "merge back to main", "ready to ship", "create a PR for this slice", "close out the slice", or "slice is done — what now". Use `prepare` to emit a readiness report; use `execute --mode direct` to also run the merge sequence; use `execute --mode pr` to push the branch and open the PR.

agentscope-ai Bundle

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

agentscope-ai Bundle

当用户需要对PDF文件进行任何操作时，请使用此技能。包括从 PDF 中读取或提取文本/表格、合并多个 PDF、拆分 PDF、旋转页面、添加水印、创建新PDF、填写PDF表单、加密/解密 PDF、提取图片，以及对扫描版 PDF 进行 OCR 使其可搜索。如果用户提到 .pdf 文件或要求生成 PDF，请使用此技能。

agentscope-ai Bundle

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

agentscope-ai Bundle

当用户需要创建、读取、编辑或处理 Word 文档（.docx）时，使用此技能。触发场景包括提到“Word 文档”、“.docx”，或要求生成带目录、标题、页码、信头等格式的专业文档；也包括提取或重组 .docx 内容、插入或替换图片、在 Word 文件中查找替换、处理修订或批注，以及将内容整理为正式 Word 文档。如果用户要求生成“报告”“备忘录”“信函”“模板”等 Word / .docx 交付物，也应使用此技能。不要用于 PDF、电子表格、Google Docs，或与文档生成无关的一般编程任务。

agentscope-ai 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; 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," 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.

agentscope-ai Bundle

当涉及到 .pptx 文件的任何操作时使用此技能——无论是作为输入、输出还是两者兼有。包括：创建幻灯片、演示文稿或路演材料；读取、解析或提取任何 .pptx 文件中的文本（即使提取的内容将用于其他地方，如邮件或摘要）；编辑、修改或更新现有演示文稿；合并或拆分幻灯片文件；处理模板、布局、演讲者备注或批注。当用户提到“演示文稿”、”幻灯片“、”PPT“或引用 .pptx 文件名时触发，无论他们之后打算如何使用内容。如果需要打开、创建或操作 .pptx 文件，就使用此技能。

agentscope-ai Skill

Answer user questions about QwenPaw installation and configuration: first locate and read local documentation, then distill the answer; if local information is insufficient, fall back to the official website documentation.

djalmajr Bundle

Tracks delivery progress in three modes — checkpoint (daily), consolidation (period report), and closure (post-implementation). Use when you need to record progress, consolidate a period, or formally close a delivery.

zhnnky329 Skill

Summarize modeling experiment evidence, compare the approved main method with a usable baseline, surface fallback triggers, and produce a decision-point or final report without creating routine per-round prose.