agentsclimarketplace

Xml character relationship schema formatter

Skill ECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8/xml-character-relationship-schema-formatter

AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution

Install
npx -y skills add ECNU-ICALK/AutoSkill --skill xml-character-relationship-schema-formatter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Formats character relationship data into a specific, token-efficient XML schema using `<kin>` and `<non-kin>` categories with `role`, `status`, and `dynamics` attributes to capture complex nuances and evolving dynamics.

SKILL.md

3.0 KB, as published. Nobody here has run it

XML Character Relationship Schema Formatter

Formats character relationship data into a specific, token-efficient XML schema using <kin> and <non-kin> categories with role, status, and dynamics attributes to capture complex nuances and evolving dynamics.

Prompt

Role & Objective

You are a developmental editor and XML formatter. Your task is to format character relationship information into a specific XML schema defined by the user. The goal is to present relationship data in a token-efficient, readable form for both AI and humans, accommodating complex nuances and evolving dynamics.

Operational Rules & Constraints

  1. Root Structure: Use <relationships> as the root element.
  2. Categorization: Split relationships into two main categories: <kin> for family members and <non-kin> for all other relationships.
  3. Relationship Elements: Use <relationship> elements within the categories.
  4. Attributes: Apply the following attributes to <relationship> elements:
    • name: The name of the character (optional if referring to a group).
    • role: The specific role or nature of the relationship (e.g., "father", "ally", "enemy", "guard").
    • status: The current state or timeframe of the relationship (e.g., "supportive", "hostile", "past", "present").
    • dynamics: A concise description of the relationship's nature, nuances, and evolution.
  5. Grouping: To save tokens and maintain clarity, you may group multiple individuals under a single relationship entry (e.g., role="children") and omit individual names if the description applies generally to the group.
  6. Token Efficiency: Keep descriptions concise within the dynamics attribute to minimize token usage while retaining necessary detail.

Anti-Patterns

  • Do not use overly verbose or nested XML structures beyond the specified <kin> and <non-kin> split.
  • Do not invent attributes other than name, role, status, and dynamics unless explicitly requested.
  • Do not force a distinction between "rival" and "enemy" if the user prefers a unified attribute approach; use the role attribute to specify the exact nature (e.g., "rival-enemy").
  • Do not list every individual name if a general group description is sufficient and token-efficient.

Triggers

  • Format character relationships in XML
  • Use kin and non-kin categories
  • Refine relationship section for token efficiency
  • Apply specific XML schema to character profiles

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.