story-copyright-detector

Classifies engineeriess into actionable blueprints for manufacturing and beyond.

178|18|Updated May 3, 2026
One-click install
npx skills add https://github.com/UfukNode/Noustiny --skill story-copyright-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-copyright-detector
Source: https://github.com/UfukNode/Noustiny/tree/main/hermes-additions/skills/creative/story-copyright-detector
Command: npx skills add https://github.com/UfukNode/Noustiny --skill story-copyright-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify a story seed to determine the appropriate rendering route for image pipelines, ensuring IP considerations are handled before rendering.

Core Features & Use Cases

  • IP risk detection: identifies known franchises or franchise-like tokens to guide model routing.
  • Single-output decision: returns a compact JSON payload with ip_level, franchise, model_preference, and reason for downstream routing.
  • Use Case: apply at canvas-enter time to route seeds with potential IP constraints to compliant pipelines; otherwise use a safe default.

Quick Start

Provide a seed input to the detector and read the resulting routing decision.

Frequently Asked Questions about story-copyright-detector

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

FAQPage Schema
How do I detect franchise IP risk in story seeds for image generation pipelines?▼

Franchise IP risk in story seeds is detected by analyzing text for known franchises or franchise-like artifacts. The detector outputs a JSON object with ip_level, franchise, model_preference, and reason to drive compliant model routing decisions.

What is IP-safe seed classification and when do I need it?▼

IP-safe seed classification categorizes story inputs to determine rendering routes before image generation. You need it at canvas-enter time to route seeds with potential IP constraints to compliant pipelines and avoid copyright violations.

How do I route image generation requests based on copyright risk levels?▼

Route image generation by reading the detector's JSON output containing ip_level and model_preference. Use these fields to direct seeds with high IP risk to compliant models while sending generic archetypes to safe default pipelines.

Can I use a single-output copyright detector for automated content moderation?▼

Yes, you can use it for automated content moderation by providing a seed input and reading the exact JSON routing decision. It outputs exactly one object containing ip_level, franchise, model_preference, and reason for downstream policy routing.

What are the limitations of automated franchise detection in image pipelines?▼

Automated franchise detection limitations include relying on identifying known franchises or franchise-like tokens in the seed text. It may classify generic archetypes as safe defaults, but complex or obscure IP references might not trigger the correct model_preference routing.

Does the story copyright detector work with existing image pipelines without dependencies?▼

Yes, the story copyright detector works with existing image pipelines without requiring external dependencies. It functions independently to classify seeds and outputs a compact JSON payload for seamless integration into your downstream routing logic.