skills.rest
Mharbulous
MharbulousCOMMUNITY
Explore all skills by this author →
GitHub

story-vetting

Detect conflicting story-tree database entries and propose merge or delete actions.

Updated Aug 27, 2026
Search Tags:#conflict#overlap#duplicate#vetting#story-tree#story-vetting
One-click install
npx skills add https://github.com/Mharbulous/SyncoPaid --skill story-vetting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-vetting
Source: https://github.com/Mharbulous/SyncoPaid/tree/main/.claude.backup-20241224/skills/story-vetting
Command: npx skills add https://github.com/Mharbulous/SyncoPaid --skill story-vetting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sqlite3, story-tree, vetting_cache, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill scans the story-tree database to detect duplicate, scope_overlap, competing, or incompatible stories and returns conflict pairs with confidence scores for human review.

Core Features & Use Cases

  • Conflict classification: identify whether pairs are duplicates, overlaps, or competing.
  • Automated actions mapping: propose deterministic actions based on conflict type and story statuses.
  • Cache & audit trail: record decisions and keep a history to improve future runs.
  • Human review workflow: surface only the cases that require human input.

Quick Start

Feed the Skill a JSON payload describing candidate story pairs and their signals, then review the generated conflict pairs and recommended actions.

Frequently Asked Questions about story-vetting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect duplicate and conflicting stories in my story database?▼

Story-vetting scans your story-tree database to identify duplicate, overlapping, or competing narratives with confidence scores. It classifies conflict types and returns pairs for review, helping prevent duplicate content before human validation.

What's the best way to automate conflict resolution in story collections?▼

Use conflict classification to map automated actions—merge, delete, block, or defer—based on conflict type and story status. Story-vetting proposes deterministic actions and surfaces only cases requiring human input, streamlining the review workflow.

Can I maintain a decision history when vetting stories for overlaps?▼

Yes. Story-vetting implements a persistent cache using SQLite that records all vetting decisions and maintains an audit trail. This history improves future runs and prevents repeated conflict analysis on already-resolved pairs.

How do I integrate story conflict detection into my generation pipeline?▼

Feed story-vetting a JSON payload with candidate story pairs and their signals when new stories are generated. It returns conflict pairs with recommended actions, letting you resolve conflicts immediately or queue them for human review.

What types of story conflicts does this Skill identify?▼

Story-vetting classifies conflicts as duplicates, scope overlaps, competing narratives, or incompatibilities. Each classification receives a confidence score and paired with story metadata to determine whether merge, deletion, blocking, deferral, or human review is appropriate.

Related Skills

Explore More Software Engineering Skills→
bivexbivex

narrative-writing

Extract narrative structure entities and hierarchical relationships from textual content.

Community
Intermediate
nathanvalenathanvale
1

format-security

Convert security audit findings into prioritized remediation tasks.

Community
Intermediate
neozenithneozenith
2

introspect

Analyze Claude Code sessions for conversation history, tool usage, and costs.

Community
Advanced
lebsrallebsral
11

ai-moderating-content

Classify user-generated content, score severity, and route moderation decisions.

Community
Advanced