skill-sensei

Standardize branded skills across Pirog and Tanaab stacks.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/pirog/me --skill skill-sensei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-sensei
Source: https://github.com/pirog/me/tree/main/skills/skill-sensei
Command: npx skills add https://github.com/pirog/me --skill skill-sensei

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Brings consistency and governance to branded skills by standardizing their structure, metadata, and icons.

Core Features & Use Cases

  • Create or standardize branded skills with a single, uniform frontmatter and folder layout.
  • Audit and optimize skill stacks for duplication, overlap, and branding consistency.
  • Propose and apply mergers, deletions, or template extraction across a skill set.

Quick Start

Run the branded skill standardization workflow to align metadata and branding across a target skill.

Frequently Asked Questions about skill-sensei

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

FAQPage Schema
How do I standardize branding and frontmatter across multiple skills?

Standardizing branded skills involves applying a uniform frontmatter layout, icon policy, and folder structure across a stack. This ensures metadata consistency and cohesive branding across all targeted skills.

What is the best way to audit skill stacks for duplication and overlap?

Auditing skill stacks for duplication involves analyzing existing skills to identify overlaps in functionality and branding. The process proposes mergers, deletions, or template extractions to optimize the set.

Can I use templates and references to enforce icon policy in new skills?

Yes, enforcing icon policy in new skills is supported by shared templates, references, and assets. These components ensure cohesive branding and adherence to workflow rules during creation.

Does this standardization workflow support consolidating doctrine across different stacks?

Consolidating doctrine across different stacks is supported by applying shared workflow rules and frontmatter layouts. This unifies governance across distinct skill sets like Pirog and Tanaab.

How do I extract templates from a set of skills to reduce workflow duplication?

Extracting templates from a skill set involves auditing workflows for duplication and consolidating shared logic. This standardizes processes and reduces redundant configuration across skills.