Case Writer Hybrid
v1.0.0Expand a structured brief in `content-production/inbox/` into a reusable long-form markdown article draft, then run a local writer / critic / judge quality l...
⭐ 0· 59·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match behavior: the skill parses brief markdown from content-production/inbox/, composes an article and writing pack, runs local quality rounds, and writes outputs under content-production/drafts (and a quality-gate path if needed). No unrelated capabilities (cloud access, external services, or unrelated system privileges) are requested.
Instruction Scope
SKILL.md and runtime instructions are narrowly scoped to reading the specified brief file, producing stage-1 drafts and sidecars, and running up to three local rounds of writer->critic->humanizer->judge. The instructions explicitly avoid downstream steps if quality fails. There are no instructions to read unrelated system files, environment variables, or to transmit data externally.
Install Mechanism
No install spec is provided (lowest-risk), but the skill includes runtime.py and depends on skill_runtime.writing_core. You should confirm how the repository is deployed and ensure required Python dependencies (e.g., skill_runtime) are from a trusted source. Overall no network download/install is embedded in the skill bundle itself.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. Its filesystem access is proportional to its purpose (reading briefs and writing drafts inside content-production).
Persistence & Privilege
always is false and the skill does not request persistent or platform-wide privileges. It does not modify other skills' configs. Autonomous invocation is allowed by default but is not combined with other concerning privileges.
Assessment
This skill appears coherent and limited to local drafting work. Before installing, verify these practical points: (1) Inspect or confirm the provenance of the skill_runtime.writing_core module and any requirements.txt used at runtime — that module does the real work and should be trusted. (2) Run the skill in a sandboxed environment (virtualenv/container) so its filesystem writes are contained. (3) Ensure briefs you place under content-production/inbox/ do not contain secrets (credentials, private keys, or sensitive PII) because the skill reads and writes those files locally. (4) If you plan to chain downstream skills (generate-image, wechat-formatter), audit those skills separately for network access or credential requests. (5) If you need higher assurance, review the rest of runtime.py (and skill_runtime.writing_core) end-to-end to confirm there are no hidden network calls or logging to external endpoints.Like a lobster shell, security has layers — review code before you run it.
latestvk9735c6j3v4zv3fahj7he2qfq584cwad
License
MIT-0
Free to use, modify, and redistribute. No attribution required.