How do I install the Solid Meta Head Management skill?

Run npx skillmds@latest add tomevault-io/solid-meta-head-management in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Solid Meta Head Management safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Solid Meta Head Management?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Solid Meta Head Management free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Solid Meta Head Management?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Solid Meta Head Management by tomevault-io

Name: Solid Meta Head Management
Author: tomevault-io

Solid Meta Head Management

Apply solid-meta head and metadata primitives with deterministic SSR-safe behavior. Use for title/meta/link/style/base management across route and layout boundaries. Use when this capability is needed.

tomevault-io a59fff9 2 files · 3.0 KB Updated Sep 17, 2026

File contents

solid-meta-head-management

Trigger

Use for metadata strategy with MetaProvider, Title, Meta, Link, Style, and related head composition requirements.

Required Inputs

Route/layout metadata ownership boundaries.
SSR and client update expectations.
SEO and social metadata requirements.

Workflow

Define metadata ownership hierarchy across app/layout/route boundaries.
Choose solid-meta primitives for each metadata type.
Document SSR-safe update expectations and collision handling.
Provide handoff to macro skill with testable metadata assertions.

Failure Modes

Multiple owners for same metadata field without precedence: resolve precedence first.
Missing SSR behavior note: output invalid.
Metadata changes without validation checks: add checks before completion.

Output Contract

Return DomainGuidanceOutput with metadata decisions, handoff steps, and citations that include normalized doc_id.

Validation

node tools/scripts/validate-skills.mjs --skill solid-meta-head-management
node tools/scripts/validate-solid-corpus.mjs

Key Corpus References

Use these doc_id values with the read_corpus_doc MCP tool:

solid-meta.solid-meta.reference.meta.metaprovider — metadata provider setup
solid-meta.solid-meta.reference.meta.title — document title management
solid-meta.solid-meta.reference.meta.meta — meta tag composition
solid-meta.solid-meta.reference.meta.link — link tag management
solid-meta.solid-meta.getting-started.server-setup — SSR metadata setup

References

../../references/solidjs-normalized/docs/solid-meta/reference/meta/metaprovider.md
../../references/solidjs-normalized/docs/solid-meta/reference/meta/title.md
../../references/solidjs-normalized/docs/solid-meta/reference/meta/meta.md
../../references/solidjs-normalized/docs/solid-meta/reference/meta/link.md
../../references/solidjs-normalized/manifest.jsonl

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: solid-meta-head-managementdescription: Apply solid-meta head and metadata primitives with deterministic SSR-safe behavior. Use for title/meta/link/style/base management across route and layout boundaries. Use when this capability is needed.---# solid-meta-head-management## TriggerUse for metadata strategy with `MetaProvider`, `Title`, `Meta`, `Link`, `Style`, and related head composition requirements.## Required Inputs- Route/layout metadata ownership boundaries.- SSR and client update expectations.- SEO and social metadata requirements.## Workflow1. Define metadata ownership hierarchy across app/layout/route boundaries.2. Choose solid-meta primitives for each metadata type.3. Document SSR-safe update expectations and collision handling.4. Provide handoff to macro skill with testable metadata assertions.## Failure Modes- Multiple owners for same metadata field without precedence: resolve precedence first.- Missing SSR behavior note: output invalid.- Metadata changes without validation checks: add checks before completion.## Output ContractReturn `DomainGuidanceOutput` with metadata decisions, handoff steps, and citations that include normalized `doc_id`.## Validation- `node tools/scripts/validate-skills.mjs --skill solid-meta-head-management`- `node tools/scripts/validate-solid-corpus.mjs`## Key Corpus ReferencesUse these `doc_id` values with the `read_corpus_doc` MCP tool:- `solid-meta.solid-meta.reference.meta.metaprovider` — metadata provider setup- `solid-meta.solid-meta.reference.meta.title` — document title management- `solid-meta.solid-meta.reference.meta.meta` — meta tag composition- `solid-meta.solid-meta.reference.meta.link` — link tag management- `solid-meta.solid-meta.getting-started.server-setup` — SSR metadata setup## References- `../../references/solidjs-normalized/docs/solid-meta/reference/meta/metaprovider.md`- `../../references/solidjs-normalized/docs/solid-meta/reference/meta/title.md`- `../../references/solidjs-normalized/docs/solid-meta/reference/meta/meta.md`- `../../references/solidjs-normalized/docs/solid-meta/reference/meta/link.md`- `../../references/solidjs-normalized/manifest.jsonl`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lvcoi) — claim your Tome and manage your conversions.

Frequently asked questions