eva-shared

Provides shared schemas, validation scripts, and examples for Eva skill modules.

54|1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Lulu-Eva/Eva-skill --skill eva-shared-lulu-eva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eva-shared
Source: https://github.com/Lulu-Eva/Eva-skill/tree/main/skills/eva-shared
Command: npx skills add https://github.com/Lulu-Eva/Eva-skill --skill eva-shared-lulu-eva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Eva's eleven user-facing skill modules need a single source of truth for asset card schemas, handoff targets, and validation logic; this package centralizes those shared files so every sibling module reads identical protocols instead of duplicating them. ## Core Features & Use Cases - Asset Card Validation: The eva_asset_validate.py script validates Eva asset cards (JSON or Markdown) against asset-card.schema.json, checking required fields, allowed source modules, valid_next handoff targets, and confidence reasons. - Local Data Backup: The eva_data_export.py script previews, exports, and verifies ZIP backups of Eva Memory, Learn, Review, and Positioning data with symlink, hidden-file, and path-traversal protections. - Shared Schemas and Examples: Ships machine-readable registries (asset-types.json, eva-link.schema.json) plus example cards and Link configs that sibling skills reference via relative paths. - Use Case: When eva-create produces a title-handoff-card, the sibling skill validates it with the shared script before passing it downstream, ensuring the card carries all required fields. ## Quick Start Install this package alongside the other Eva skills so modules like eva-create and eva-memory can read the shared schemas and run the validation scripts.

Frequently Asked Questions about eva-shared

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

FAQPage Schema
How do I validate an Eva asset card against the schema?

Run scripts/eva_asset_validate.py with --asset pointing to a JSON or Markdown card file. The script checks required fields, allowed source modules, valid_next handoff targets, and low-confidence reasons, then prints a JSON result with errors and warnings.

What is eva-shared used for in the Eva skill system?

eva-shared is the shared source package for Eva-skill 2.4.2, not a user-facing entry. Sibling skills like eva-create and eva-memory read its schemas, references, and scripts through relative paths so all modules use identical protocols.

Can I use eva-shared directly for content creation tasks?

No. The SKILL.md explicitly forbids direct invocation and routing user tasks to it. Use /eva or a specific entry such as eva-think, eva-create, or eva-review instead; eva-shared only supplies shared files to those modules.

Does the Eva data export script require third-party Python packages?

No. eva_data_export.py uses only the Python standard library. It previews, exports, and verifies local ZIP backups of Memory, Learn, Review, and Positioning data with protections against symlinks, hidden files, and path traversal.

Why does asset validation fail for a product-service-card?

product-service-card has extra requirements: a valid profile_id, positive integer revision, facts_confirmed_at date, lifecycle_status, structured core_content fields, and non-empty evidence with a valid status. Revision 1 must not declare supersedes, while higher revisions require it.