skills.rest
tylersahagun
tylersahagunCOMMUNITY
Explore all skills by this author →
GitHub

myeducator-xml

Enforce MyEducator XML scope and ID preservation within the book directory.

Updated Aug 27, 2026
Search Tags:#xml#manuscript#guardrails#content editing#myeducator#id preservation
One-click install
npx skills add https://github.com/tylersahagun/proj-marriot --skill myeducator-xml
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: myeducator-xml
Source: https://github.com/tylersahagun/proj-marriot/tree/main/.agents/skills/myeducator-xml
Command: npx skills add https://github.com/tylersahagun/proj-marriot --skill myeducator-xml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that edits made to the MyEducator XML manuscript adhere to specific project constraints and maintain the integrity of the book's structure and MyEducator compatibility.

Core Features & Use Cases

  • Scope Enforcement: Restricts operations to the designated book/ directory.
  • Legacy Area Prevention: Prevents accidental modification or referencing of outdated project sections.
  • XML Validity: Guides users to maintain syntactically correct and MyEducator-compliant XML.
  • ID Preservation: Emphasizes the critical importance of not altering existing id="" attributes.
  • Use Case: An AI agent is tasked with updating a chapter. This Skill acts as a guardrail, ensuring the agent only modifies the correct XML files and preserves essential identifiers, preventing import errors on the MyEducator platform.

Quick Start

Ensure all edits are confined to the book/ directory and preserve existing id="" attributes.

Frequently Asked Questions about myeducator-xml

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

FAQPage Schema
How do I maintain MyEducator XML manuscript integrity when editing book files?▼

To maintain MyEducator XML manuscript integrity, restrict all content edits to active files within the designated book directory and preserve existing id attributes to ensure seamless platform imports without structural errors.

Why does MyEducator XML import fail after automated content editing?▼

MyEducator XML imports fail when id attributes are altered or deleted during content editing. Preserving these exact identifiers and maintaining strict XML tag structure prevents import errors on the platform.

What is the best way to prevent an AI agent from modifying legacy XML areas?▼

Preventing AI agents from modifying legacy XML areas requires applying scope guardrails that restrict operations exclusively to the active book directory, avoiding any reference to outdated project sections.

Do I need to keep XML edits confined to the book directory for MyEducator?▼

Yes, you need to keep XML edits confined to the book directory. Operating exclusively within this scope prevents accidental modification of legacy areas and ensures MyEducator XML validity.

What happens if existing id attributes are changed during MyEducator XML editing?▼

Changing existing id attributes during MyEducator XML editing breaks manuscript integrity and causes import errors. Strict ID preservation is required to maintain compatibility and seamless MyEducator imports.

Related Skills

Explore More Content & Communication Skills→
alexsandrocruzalexsandrocruz

code-review-excellence

Generate structured, actionable code review feedback for .NET, TypeScript, and React pull requests.

Community
Basic
Nikolay-ShirokovNikolay-Shirokov
511

mxl-validate

Validate 1C MXL spreadsheet template XML structure against platform rules.

Community
Intermediate
Victory-HugoVictory-Hugo
1

peer-review

Evaluate scientific manuscripts through a structured peer-review workflow with checklists and reporting standards.

Community
Advanced
cipherstashcipherstash
17

Maintaining Documentation After Code Changes

Synchronize project documentation with code changes using a two-phase workflow.

Official
Intermediate