
Content Management
- 1 installs
- Updated June 26, 2026
- bivex/loresystem
content-management is a Claude skill that extracts content-management entities such as mods, maps, localization, and subtitles from narrative text.
About
This skill extracts content-management entities from narrative text as part of an entity-extraction system. It recognizes 10 entity types such as mods, custom maps, user scenarios, localization, translations, subtitles, and dubbing, and emits schema-compliant JSON. A developer uses it when analyzing text for user-generated content, localization, and audio/visual assets.
- Extracts content-management entities from narrative text (mods, maps, localization, subtitles, dubbing)
- Defines 10 entity types with schema-compliant JSON output
- Domain skill for a Content Creator entity-extraction system
Content Management by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,803 of 2,064 Data Science & ML skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
What content-management says it does
Extract content management entities from narrative text. Use when analyzing mods, custom maps, user scenarios, localization, translations, subtitles, dubbing, and workshop content.
## Entity Types (10 total)
Create schema-compliant entities** with proper JSON structure
npx skills add https://github.com/bivex/loresystem --skill content-managementAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | June 26, 2026 |
| Repository | bivex/loresystem ↗ |
What it does
Extract content-management entities (mods, maps, localization, subtitles, dubbing) from narrative text as structured JSON.
Who is it for?
Extracting content and localization entities from chapter or narrative text.
When should I use this skill?
Use when analyzing mods, custom maps, user scenarios, localization, translations, subtitles, dubbing, and workshop content.
What you get
Schema-compliant JSON entities for mods, maps, scenarios, localization, and audio/visual content.
- schema-compliant JSON entities
By the numbers
- 10 total entity types
- entity types include mod, custom_map, workshop_entry, localization, dubbing
Files
content-management
Domain skill for Content Creator. Specific extraction rules and expertise.
Domain Expertise
- Modding: User modifications, custom content
- Maps: Custom levels, world design
- UGC platforms: Workshops, sharing systems
- Localization: Translating content for different regions
- Audio/visual: Subtitles, dubbing, voice over
- Content pipelines: Creation, testing, distribution
Entity Types (10 total)
- mod - Mods and modifications
- custom_map - Custom maps
- user_scenario - User-created scenarios
- share_code - Share codes
- workshop_entry - Workshop entries
- localization - Localization settings
- translation - Translations
- subtitle - Subtitles
- dubbing - Dubbing tracks
- voice_over - Voice over
Processing Guidelines
When extracting content entities from chapter text:
1. Identify content elements:
- Mods or custom content mentioned
- Custom maps or user scenarios
- Workshop or sharing platforms
- Localization needs (different languages)
- Audio/visual requirements (subtitles, dubbing)
2. Extract content details:
- Mod types and features
- Map designs and objectives
- Sharing mechanisms and codes
- Translation requirements
- Audio/visual specifications
3. Analyze content context:
- Platform compatibility
- Content rating/approval
- Community standards
- Technical constraints
4. Create schema-compliant entities with proper JSON structure
Key Considerations
- Platform differences: Content may work differently on different platforms
- Community standards: Mods may be rejected for violations
- Translation quality: Direct translations may miss cultural context
- Technical constraints: File sizes, compatibility, performance