Skip to content

feat: add quality scoring, core principles, and 3 wiki-sourced patterns#94

Open
Charpup wants to merge 1 commit intoblader:mainfrom
Charpup:feat/quality-scoring-and-wiki-patterns
Open

feat: add quality scoring, core principles, and 3 wiki-sourced patterns#94
Charpup wants to merge 1 commit intoblader:mainfrom
Charpup:feat/quality-scoring-and-wiki-patterns

Conversation

@Charpup
Copy link
Copy Markdown

@Charpup Charpup commented Apr 15, 2026

Summary

  • Quality Scoring System (/50, 5 dimensions): Directness, Rhythm, Reader Trust, Authenticity, Conciseness. Adapted from Humanizer-zh / stop-slop.
  • 5 Core Principles quick reference: Delete filler, Break formula, Vary rhythm, Trust the reader, Kill the quotables.
  • 6-item Quick Checklist for pre-delivery audit (sentence length, paragraph endings, em dashes, metaphor trust, connectors, rule of three).
  • 3 new patterns (P30-P32) sourced from Wikipedia: Signs of AI writing and WikiProject AI Cleanup:
    • P30: Citation Fabrication / Hallucinated Sources
    • P31: Broken Markup Artifacts
    • P32: Era-Specific Vocabulary Clustering
  • Detection Confidence Framework: Categorizes all 32 patterns by signal strength (HIGH/MEDIUM/LOW) with a combined indicator principle.

Motivation

These additions make the skill more actionable in practice:

  • The scoring system gives writers a concrete target (≥40/50) instead of subjective judgment
  • Core principles and checklist speed up the self-editing loop
  • Wikipedia-sourced patterns cover detection gaps (especially citation hallucination and markup artifacts) that the current 29 patterns miss
  • The confidence framework helps prioritize which patterns matter most

All new content is English-only and maintains the existing style/structure.

Test plan

  • Verify YAML frontmatter still parses correctly
  • Verify new patterns (30-32) appear in correct location after Pattern 29
  • Verify scoring, principles, checklist, and confidence framework sections are placed after Output Format
  • Test with sample AI-generated text to confirm new patterns are detected

🤖 Generated with Claude Code

…rced patterns

Adds practical rewriting tools adapted from Humanizer-zh/stop-slop (quality
scoring /50, 5 core principles, pre-delivery checklist) and 3 new patterns
sourced from Wikipedia's Signs of AI Writing article (citation fabrication,
broken markup artifacts, era-specific vocabulary clustering).

Also adds a detection confidence framework that categorizes all 32 patterns
by signal strength (HIGH/MEDIUM/LOW).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Charpup added a commit to Charpup/openclaw-task-workflow that referenced this pull request Apr 18, 2026
Round-2 standardization pass. All additions additive; no breaking changes.

## Changes

### examples/humanizer-skill-schedule/ (new)
Real completed run from the humanizer-skill build (PR blader/humanizer#94 merged).
21 tasks across 9 author-defined batches, which the scheduler reshapes into 12
dependency-aware batches. 4 files:

- README.md: explains GOLD labeling and characteristic lessons
- input-task_plan.md: verbatim snapshot of the real plan
- output-schedule.json: full DAG output with tasks_extracted, batches,
  batch_metadata (parallelism + max complexity per batch + notes), summary
  (critical path, complexity sum, max parallelism)
- output-handoff-snippet.json: how the same schedule lives inside
  triadev-handoff.json (excerpt, planning + scheduling sections only)

Demonstrates fan-out (T7 → 5 downstream refs), fan-in (T13 ← 5 refs),
within-batch complexity ordering (T1=1, T2=1, T16=1, T6=4 in batch 1).

### evals/evals.json (4 → 8 cases)
New coverage:
- batch-ordering-complexity-01: verifies within-batch tasks are ordered
  ascending by complexity (no-dep tasks only)
- cross-session-persistence-01: CST 00:00 migration — completed tasks stay,
  running + pending get "migrated" status and carried over
- standalone-mode-01: task-workflow works without triadev-handoff.json,
  reading task_plan.md directly; must NOT create triadev-handoff.json
- dynamic-insertion-01: mid-execution insertion of a new task; only
  remaining (non-completed) tasks get re-scheduled

Assertion types shifted:
- Added sequence_order type for batch ordering verification
- Added json_path_length for assertion on batches array size
- ~80% of assertions now deterministic (file_exists, json_path_*, sequence_order,
  contains_all/any, does_not_contain) vs ~20% llm_judge (was 50/50 in v3.1)

### README.md
Full rewrite aligning with sister-skill docs. Adds What's New in v3.2 table,
Working Example callout, changelog v3.2 entry.

## Verification

- 3 new JSON files parse cleanly
- Example schedule consistent with SKILL.md's batch-ordering rules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant