ワンクリックでManusで任意のスキルを実行

openwiki-proposal-drafting

スター10

フォーク1

更新日2026年7月18日 09:20

Use when drafting reviewable OpenWiki proposals from retrieved evidence, link suggestions, schema-pack requirements, or inbox-derived material.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

joe-broadhead

joe-broadhead/open-cowork

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

OpenWiki Proposal Drafting

Use this skill when a change should be staged for human review.

Required behavior:

Search and read existing records before drafting.
Preserve page IDs, source IDs, claim IDs, proposal IDs, and inbox IDs in rationale text when they justify the change.
Draft focused proposals. Prefer one proposal per page-sized change.
Keep canonical page bodies in Markdown and let OpenWiki render frontmatter.
Use schema-pack guidance as constraints, not as permission to bypass repository validation.
After every proposal, read the proposal detail and report validation status, target path, and any warnings.
Do not apply proposals unless the user explicitly authorizes trusted write mode.

When link extraction suggests an edge, include the extraction rule and confidence in the rationale or a suggested-links section so reviewers can distinguish explicit links from derived ones.

このリポジトリの他の Skills

同じリポジトリ

gateway-assistant

joe-broadhead/open-cowork

User-facing Gateway assistant for OpenCode, Telegram, and WhatsApp sessions. Use when the user asks normal Gateway questions, wants to create or manage durable work, asks what needs attention, or interacts from a linked channel.

2026-07-1810

gateway-coordinator

joe-broadhead/open-cowork

Coordinate Gateway queues, runs, channel bindings, requests, and service state.

2026-07-1810

gateway-planner

joe-broadhead/open-cowork

Plan Gateway roadmaps and durable scheduler tasks using Gateway MCP tools.

2026-07-1810

gateway-review-gate

joe-broadhead/open-cowork

Spec-driven review and verification gate for Gateway tasks across code, docs, slides, research, operations, and other deliverables.

2026-07-1810

gateway-stage

joe-broadhead/open-cowork

Execute a Gateway scheduler stage and return the required structured stage result.

2026-07-1810

gateway-supervisor

joe-broadhead/open-cowork

Supervise a durable Gateway roadmap using event cursors, roadmap memory, and safe action proposals.

2026-07-1810

name	openwiki-proposal-drafting
description	Use when drafting reviewable OpenWiki proposals from retrieved evidence, link suggestions, schema-pack requirements, or inbox-derived material.
version	1.0.0
applies_to	["opencode","openclaw","mcp"]
required_tools	["wiki.search","wiki.read_page","wiki.read_source","wiki.propose_edit","wiki.propose_synthesis","wiki.read_proposal_detail"]
allowed_operations	["wiki.search","wiki.ask","wiki.think","wiki.read_page","wiki.read_source","wiki.read_claim","wiki.trace_claim","wiki.graph_neighbors","wiki.graph_related","wiki.propose_edit","wiki.propose_synthesis","wiki.propose_source","wiki.read_proposal_detail","wiki.comment_on_proposal"]
risk_level	medium

OpenWiki Proposal Drafting

Use this skill when a change should be staged for human review.

Required behavior:

Search and read existing records before drafting.
Preserve page IDs, source IDs, claim IDs, proposal IDs, and inbox IDs in rationale text when they justify the change.
Draft focused proposals. Prefer one proposal per page-sized change.
Keep canonical page bodies in Markdown and let OpenWiki render frontmatter.
Use schema-pack guidance as constraints, not as permission to bypass repository validation.
After every proposal, read the proposal detail and report validation status, target path, and any warnings.
Do not apply proposals unless the user explicitly authorizes trusted write mode.

When link extraction suggests an edge, include the extraction rule and confidence in the rationale or a suggested-links section so reviewers can distinguish explicit links from derived ones.