ReddRadar
Topic: tools
135 skills in this topic.
-
kirby-panel-and-blueprints
Designs Kirby blueprints and Panel UI, including blueprint reuse/extends, programmable blueprints, and custom Panel fields/sections/areas. Use when changing the Panel experience or schema.
bnomei/kirby-mcp 40
-
kirby-scaffold-page-type
Scaffolds a new Kirby page type (blueprint + template, optional controller/model) using project roots, index tools, and Panel field/section references. Use when creating a new page type or extending an existing blueprint/template.
bnomei/kirby-mcp 40
-
kirby-routing-and-representations
Implements custom Kirby routes and content representations (.json/.xml/.rss), including redirects, sitemap endpoints, and URL pattern filtering. Use when building endpoints, redirects, or representation templates that change how URLs resolve.
bnomei/kirby-mcp 40
-
kirby-headless-api
Exposes Kirby content to headless clients using the API, KQL, and JSON representations. Use when building API endpoints, KQL queries, or headless frontends.
bnomei/kirby-mcp 40
-
kirby-upgrade-and-maintenance
Upgrades Kirby and maintains dependencies safely using composer audit, plugin compatibility checks, and official docs. Use when updating Kirby versions or making maintenance changes that affect runtime.
bnomei/kirby-mcp 40
-
kirby-security-and-auth
Secures Kirby sites with access restriction, user roles, permissions, and protected downloads. Use when implementing login/role-based access, permissions, or file protection.
bnomei/kirby-mcp 40
-
kirby-performance-and-media
Improves Kirby performance and media delivery (cache tuning, CDN, responsive images, lazy loading). Use when optimizing page speed, caching, or image handling.
bnomei/kirby-mcp 40
-
kirby-project-tour
Maps a Kirby project using Kirby MCP tools/resources, including roots, templates, snippets, controllers, models, blueprints, plugins, runtime status, and key config. Use when a user wants a project overview, file locations, or a quick orientation before making changes.
bnomei/kirby-mcp 40
-
kirby-content-migration
Plans and applies safe Kirby content migrations using runtime content tools, update schemas, and explicit confirmation. Use when users need to rename/move/transform fields, clean up content, or bulk-update pages/files across languages.
bnomei/kirby-mcp 40
-
kirby-collections-and-navigation
Builds Kirby listings, pagination, search, filtering/sorting/grouping, and navigation menus. Use when implementing collection logic in templates/controllers/snippets.
bnomei/kirby-mcp 40
-
kirby-plugin-development
Builds or extends Kirby plugins using hooks, extensions, blocks, KirbyTags, and shared templates/controllers. Use when creating reusable features or integrating Panel customizations.
bnomei/kirby-mcp 40
-
evidence-binder
Bind addressable evidence IDs from `papers/evidence_bank.jsonl` to each subsection (H3), producing `outline/evidence_bindings.jsonl`.
**Trigger**: evidence binder, evidence plan, section->evidence mapping, 证据绑定, evidence_id.
**Use when**: `papers/evidence_bank.jsonl` exists and you want writer/auditor to use section-scoped evidence items (WebWeaver-style memory bank).
**Skip if**: you are not doing evidence-first section-by-section writing.
**Network**: none.
**Guardrail**: NO PROSE; do not invent evidence; only select from the existing evidence bank.
WILLOSCAR/research-units-pipeline-skills 377
-
latex-compile-qa
Compile a LaTeX project and run basic QA (missing refs, bib errors, broken citations), producing `latex/main.pdf` and a build report.
**Trigger**: latex compile, build PDF, LaTeX errors, missing refs, 编译PDF, 引用错误.
**Use when**: 已有 `latex/main.tex`（通常来自 `latex-scaffold`），需要确认可编译并输出失败原因报告。
**Skip if**: 还没有 LaTeX scaffold（先跑 `latex-scaffold`）。
**Network**: none.
**Guardrail**: 编译失败也要落盘 `output/LATEX_BUILD_REPORT.md`；不做“内容改写”，只做编译/QA。
WILLOSCAR/research-units-pipeline-skills 377
-
outline-budgeter
Merge/simplify an over-fragmented outline to hit a paper-like section budget (NO PROSE): target final ToC ~6–8 H2, fewer thicker H3.
**Trigger**: outline budget, merge sections, too many sections, H3 explosion, 大纲预算, 合并小节, 大纲太碎.
**Use when**: `outline/outline.yml` exists but would produce thin sections (too many H2/H3); before (or immediately after) `section-mapper`.
**Skip if**: outline is already within budget and approved; or you are already drafting prose.
**Network**: none.
**Guardrail**: NO PROSE; do not invent new topics; keep scope consistent; if you change section ids, you must reset mapping.
WILLOSCAR/research-units-pipeline-skills 377
-
terminology-normalizer
Normalize terminology across a draft (canonical terms + synonym policy) without changing citations or meaning.
**Trigger**: terminology, glossary, consistent terms, 术语统一, 统一叫法, 术语表.
**Use when**: the draft has concept drift (same thing called 2–3 names) or global-review flags terminology inconsistency.
**Skip if**: you are still changing the outline/taxonomy heavily (do that first).
**Network**: none.
**Guardrail**: do not add/remove citation keys; do not introduce new claims; avoid moving citations across subsections.
WILLOSCAR/research-units-pipeline-skills 377
-
thesis-style-polisher
对中文毕业论文做最终润色与去 AI 味：重点处理章首导言、章末小结、贡献描述、总结与展望中的模板腔、宣传腔与 AI 口癖。
**Trigger**: 论文润色, thesis style polish, 去 AI 味, 中文论文风格统一, 章首导言润色, 总结展望润色.
**Use when**: 结构、证据、数据和编译已经基本稳定，需要做最后一轮中文学位论文风格收口。
**Skip if**: 正文结构还在大改，或关键引用 / 数字 / 图表还没稳定。
**Network**: none.
**Guardrail**: 不用润色掩盖结构问题；不引入新事实；先去模板腔，再做措辞提升。
WILLOSCAR/research-units-pipeline-skills 377
-
human-checkpoint
Record a human sign-off at a declared checkpoint (tick `Approve C*` in `DECISIONS.md`) so the pipeline can resume.
**Trigger**: approve checkpoint, human approval, sign off, HITL, Approve C2, 审批, 签字, 人类检查点.
**Use when**: A unit has `owner=HUMAN` and is BLOCKED waiting for a checkbox in `DECISIONS.md`.
**Skip if**: The approval is already recorded (the checkbox is ticked).
**Network**: none.
**Guardrail**: Do not modify any content artifacts; only update `DECISIONS.md` (and optionally append a short sign-off note).
WILLOSCAR/research-units-pipeline-skills 377
-
subsection-polisher
Polish a single H3 unit file under `sections/` into survey-grade prose (de-template + contrast/eval/limitation), without changing citation keys.
**Trigger**: subsection polisher, per-subsection polish, polish section file, 小节润色, 去模板, 结构化段落.
**Use when**: `sections/S*.md` exists but reads rigid/template-y; you want to fix quality locally before `section-merger`.
**Skip if**: subsection files are missing, evidence packs are incomplete, or `Approve C2` is not recorded.
**Network**: none.
**Guardrail**: do not invent facts/citations; do not add/remove citation keys; keep citations within the same H3; keep citations subsection-scoped.
WILLOSCAR/research-units-pipeline-skills 377
-
_template_reference_first
Internal template for creating or refactoring a skill into the repository's reference-first shape.
**Trigger**: reference-first template, blueprint skill, create a reusable skill, refactor a script-heavy skill.
**Use when**: you need a lean `SKILL.md`, explicit `references/`, machine-readable `assets/`, and a minimal deterministic `run.py`.
**Skip if**: the task is a one-off workflow that will not be reused as a skill.
**Network**: none.
**Guardrail**: keep domain knowledge and writing exemplars out of `run.py`; make reference loading explicit; do not ship reader-facing placeholder text.
WILLOSCAR/research-units-pipeline-skills 377
-
claim-matrix-rewriter
Rewrite `outline/claim_evidence_matrix.md` as a projection/index of evidence packs (NO PROSE), so claims/axes are driven by `outline/evidence_drafts.jsonl` rather than outline placeholders.
**Trigger**: claim matrix rewriter, rewrite claim-evidence matrix, evidence-first claim matrix, matrix index, 证据矩阵重写, 从证据包生成矩阵.
**Use when**: `outline/subsection_briefs.jsonl` + `outline/evidence_drafts.jsonl` are ready and you want a clean claim→evidence index for QA/writing.
**Skip if**: `outline/claim_evidence_matrix.md` is already refined and consistent with evidence packs.
**Network**: none.
**Guardrail**: NO PROSE; do not invent facts; only cite keys present in `citations/ref.bib`; if evidence is abstract/title-only, claims must be provisional.
WILLOSCAR/research-units-pipeline-skills 377
-
chapter-briefs
Build per-chapter (H2) writing briefs (NO PROSE) so the final survey reads like a paper (chapter leads + cross-H3 coherence) without inflating the ToC.
**Trigger**: chapter briefs, H2 briefs, chapter lead plan, section intent, 章节意图, 章节导读, H2 卡片.
**Use when**: `outline/outline.yml` + `outline/subsection_briefs.jsonl` exist and you want thicker chapters (fewer headings, more logic).
**Skip if**: the outline is still changing heavily (fix outline/mapping first).
**Network**: none.
**Guardrail**: NO PROSE; do not invent papers; only reference subsection ids and already-mapped papers.
WILLOSCAR/research-units-pipeline-skills 377
-
post-merge-voice-gate
Post-merge paper-voice gate: detect planner-talk / axis-label artifacts introduced during merge (especially from `outline/transitions.md`), then route fixes back to the earliest source.
**Trigger**: post-merge voice gate, merge voice gate, transition leakage, planner talk, 合并后口吻门, 过渡句污染.
**Use when**: `section-merger` has produced `output/DRAFT.md` and you want to ensure merge-injected text won't drag the draft into generator voice before polishing.
**Skip if**: you are still pre-merge (no `output/DRAFT.md`) or you plan to rework structure upstream first.
**Network**: none.
**Guardrail**: analysis-only; do not edit `output/DRAFT.md`; do not invent facts/citations; write only the report + routing.
WILLOSCAR/research-units-pipeline-skills 377
-
section-bindings
Bind papers to chapter-level sections first, writing `outline/section_bindings.jsonl` and `outline/section_binding_report.md`.
**Trigger**: section bindings, chapter bindings, section-first binding, 章节绑定, 章级绑定.
**Use when**: survey structure should measure chapter saturation before stable H3 decomposition.
**Skip if**: chapter skeleton is missing or the bindings are already refined.
**Network**: none.
**Guardrail**: NO PROSE; do not invent papers; produce auditable PASS/BLOCKED/REROUTE signals.
WILLOSCAR/research-units-pipeline-skills 377
-
unit-planner
Instantiate or update a workspace `UNITS.csv` from a selected pipeline and units template (deps/checkpoints/acceptance).
**Trigger**: unit planner, generate UNITS.csv, execution contract, units template, 生成工作单元.
**Use when**: 初始化/更新执行合同：从 pipeline 选择生成 `UNITS.csv`，或 scope 扩展需要新增 units/依赖。
**Skip if**: `UNITS.csv` 已正确反映当前 scope（无需重写）。
**Network**: none.
**Guardrail**: 保持 CSV 合法；scope 增长时新增 units；只在满足验收后标 `DONE`。
WILLOSCAR/research-units-pipeline-skills 377