lore-extraction — civilization lore-extraction, loreSystem, community, civilization, ide skills, creation, creative, fiction, storytelling, toolkit

v1.0.0

이 스킬 정보

고급적인 내러티브 텍스트 분석 및 엔티티 추출 기능이 필요한 월드빌딩 에이전트에게 완벽함 Base extraction rules for all lore subagents. Governs entity identification, contextual analysis, relationship mapping, and JSON output formatting.

# Core Topics

bivex bivex
[0]
[0]
Updated: 3/21/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
29
Canonical Locale
en
Detected Body Locale
en

고급적인 내러티브 텍스트 분석 및 엔티티 추출 기능이 필요한 월드빌딩 에이전트에게 완벽함 Base extraction rules for all lore subagents. Governs entity identification, contextual analysis, relationship mapping, and JSON output formatting.

이 스킬을 사용하는 이유

에이전트가 내러티브 텍스트에서 엔티티를 추출하여 엔티티 소유권 맵에 따라 분류하고 LoreData.to_dict와 호환되는 JSON 형식으로 출력할 수 있게 하며, 표준화된 추출 파이프라인을 활용하고 JSON 등의 프로토콜을 지원함

최적의 용도

고급적인 내러티브 텍스트 분석 및 엔티티 추출 기능이 필요한 월드빌딩 에이전트에게 완벽함

실행 가능한 사용 사례 for lore-extraction

내러티브 텍스트에서 엔티티를 추출하여 몰입형 우주를 생성함
엔티티 간의 관계를 식별하고 분류하여 문명을 설계함
월드빌딩 프로젝트의 엔티티 소유권 맵을 자동으로 구축함

! 보안 및 제한 사항

  • 추출 전에 완전한 소스 텍스트를 읽어야 함
  • 내러티브 텍스트 분석에만 제한됨
  • 분류를 위해 미리 정의된 엔티티 소유권 맵이 필요함

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is lore-extraction?

고급적인 내러티브 텍스트 분석 및 엔티티 추출 기능이 필요한 월드빌딩 에이전트에게 완벽함 Base extraction rules for all lore subagents. Governs entity identification, contextual analysis, relationship mapping, and JSON output formatting.

How do I install lore-extraction?

Run the command: npx killer-skills add bivex/loreSystem/lore-extraction. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for lore-extraction?

Key use cases include: 내러티브 텍스트에서 엔티티를 추출하여 몰입형 우주를 생성함, 엔티티 간의 관계를 식별하고 분류하여 문명을 설계함, 월드빌딩 프로젝트의 엔티티 소유권 맵을 자동으로 구축함.

Which IDEs are compatible with lore-extraction?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for lore-extraction?

추출 전에 완전한 소스 텍스트를 읽어야 함. 내러티브 텍스트 분석에만 제한됨. 분류를 위해 미리 정의된 엔티티 소유권 맵이 필요함.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add bivex/loreSystem/lore-extraction. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use lore-extraction immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

lore-extraction

Install lore-extraction, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

lore-extraction

Base skill for all loreSystem extraction subagents. Common rules for extracting entities from narrative text.

Extraction Pipeline

  1. Read the source text completely before extracting
  2. Identify entities — look for named things, described systems, relationships
  3. Classify each entity to its correct type from the entity ownership map
  4. Format according to the export schema
  5. Output as JSON compatible with LoreData.to_dict (see src/presentation/gui/lore_data.py)
  6. Validate against domain model constraints
  7. Review for completeness and accuracy

Entity Identification Rules

  • Named entities (proper nouns, titles) → extract with exact name
  • Described systems (magic system, economy) → extract with descriptive name
  • Implied entities (unnamed but significant) → extract with contextual name
  • Groups/collections → extract as single entity with members in description

Cross-Domain References

When text mentions an entity owned by another skill:

  • Do NOT create the entity — it belongs to the other skill
  • Record the reference in a separate draft note for the lead to merge
  • Include enough context (name, location, relation) for reconciliation

Quality Rules

  • Extract only what the text explicitly states or strongly implies
  • Do not invent details not supported by the text
  • If unsure, add a short comment in your draft note (not in the JSON export)
  • Prefer fewer high-quality entities over many low-quality ones

관련 스킬

Looking for an alternative to lore-extraction or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자