rs-shared

Consolidate shared utilities, fragments, and scripts for RootSpec skill workflows.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/rootspec/rootspec --skill rs-shared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rs-shared
Source: https://github.com/rootspec/rootspec/tree/main/skills/rs-shared
Command: npx skills add https://github.com/rootspec/rootspec --skill rs-shared

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires js-yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Shared resources, including scripts, fragments, and bundled files, are provided for all RootSpec skills to prevent duplication and promote consistency across projects.

Core Features & Use Cases

  • Centralized access to common tooling for spec extraction, validation, and test scaffolding.
  • A curated collection of fragments and references that standardize conventions, guidance, and cross-skill workflows.
  • Lightweight, shareable assets that accelerate onboarding and collaboration across teams.

Quick Start

Reference this skill from your RootSpec project to access shared resources and avoid duplicating common tooling.

Frequently Asked Questions about rs-shared

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

FAQPage Schema
How do I prevent duplication of shared validation scripts across multiple specification projects?

Consolidating shared validation scripts in a central repository prevents duplication by exposing common tooling and fragments that all RootSpec skills reference, ensuring consistent specification behavior across projects. Individual projects can override or extend these shared primitives as needed.

What are shared specification fragments and when do I need them for automation workflows?

Shared specification fragments are standardized reference materials and helper scripts that standardize conventions across automation workflows. You need them when multiple skills require consistent design pillar extraction, validation, and test scaffolding without duplicating tooling logic in every project setup.

How do I set up a RootSpec project to use shared tooling and reference materials?

Reference this skill from your RootSpec project to access shared resources, avoiding the need to duplicate common tooling. This grants centralized access to spec extraction utilities, validation scripts, and standard fragments that streamline onboarding and collaboration across teams.

Does this shared tooling require specific dependencies to run validation scripts?

The shared validation scripts and tooling require the js-yaml dependency to function. This lightweight library allows the bundled scripts and helper utilities to parse, extract, and validate YAML-based specification files and design pillars across your project workflows.

Can I override shared fragments and validation scripts for individual project contexts?

Yes, individual projects can override or extend the shared fragments and validation scripts as needed. While the skill provides common primitives and standard references to ensure consistent behavior by default, project-specific contexts can adapt the tooling without affecting the centralized source.

What is the best way to standardize spec extraction and test scaffolding across teams?

The best way to standardize spec extraction and test scaffolding is using a centralized collection of shared fragments and scripts. Providing common primitives and reference materials ensures consistent conventions and cross-skill workflows, accelerating team onboarding and collaboration.