shared

Standardize TodoWrite patterns, evidence formats, and analysis workflows across imbue skills.

326|35|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/athola/claude-night-market --skill shared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared
Source: https://github.com/athola/claude-night-market/tree/main/plugins/imbue/skills/shared
Command: npx skills add https://github.com/athola/claude-night-market --skill shared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides shared infrastructure patterns used by other imbue analysis skills to ensure consistency, reproducibility, and easier collaboration.

Core Features & Use Cases

  • TodoWrite patterns for consistent task tracking
  • Evidence formats for standardized logging
  • Shared analysis workflows to unify approaches across imbue skills

Quick Start

Example: Use imbue:evidence-logging and shared patterns when authoring a new imbue skill to ensure consistent naming and evidence trails.

Frequently Asked Questions about shared

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

FAQPage Schema
How do I ensure consistent analysis patterns across multiple imbue skills?

Shared patterns provide standardized infrastructure for analysis workflows, evidence formats, and TodoWrite task tracking across imbue, pensive, and sanctum plugins. This ensures reproducible outputs and unified naming conventions when authoring or integrating new skills.

What evidence formats should I use when building a new imbue skill?

The shared infrastructure defines standardized evidence logging formats that work across imbue skills. Using these formats ensures your skill produces consistent, traceable evidence trails compatible with existing analysis workflows and modular integration patterns.

Can I apply shared infrastructure patterns to existing imbue skills?

Yes, shared patterns apply to both new and existing imbue, pensive, and sanctum skills. They enable retroactive standardization of TodoWrite task tracking, evidence handling, and analysis workflows without requiring a complete skill rewrite.

Why is consistent naming important across imbue skills?

Consistent naming conventions reduce cognitive overhead when switching between skills and enable easier collaboration. The shared infrastructure enforces these conventions across TodoWrite patterns and evidence formats, improving reproducibility and maintainability.

How do shared workflows improve skill modularity?

Shared analysis workflows create standardized integration points across skills, enabling modular composition and reducing coupling. This allows new skills to leverage proven patterns and evidence handling approaches instead of building custom infrastructure.