playbooks

home / skills / williamzujkowski / standards / missing-level1

missing-level1 skill

/tests/scripts/fixtures/skills/missing-level1

This skill helps you implement missing Level 1 sections by guiding Python projects from setup to foundational design, ensuring consistency with production

npx playbooks add skill williamzujkowski/standards --skill missing-level1

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
195 B
---
name: missing-level1
description: A skill missing Level 1 section
version: 1.0.0
---

# Missing Level 1 Skill

## Level 2: Implementation

This skill is missing the required Level 1 section.

Overview

This skill detects and fixes a missing Level 1 section in a standards or documentation skill. It helps maintain the required top-level documentation structure so projects start with a consistent, minimal entry point. The skill offers templates and concrete suggestions to create a compliant Level 1 section quickly.

How this skill works

The skill scans the repository for a top-level Level 1 heading and verifies that it contains required elements such as purpose, scope, and quick start notes. If the Level 1 section is absent or incomplete, it generates a concise Level 1 draft based on repository metadata and common standards. It can output editable text or apply the change directly when configured to do so.

When to use it

  • Onboarding new project templates to ensure consistent documentation structure.
  • During CI checks to enforce presence of a Level 1 heading before merge.
  • When auditing repositories to bring documentation up to standards.
  • Before publishing or releasing to ensure minimal user-facing docs exist.
  • When converting informal notes into a structured standards skill.

Best practices

  • Keep the Level 1 section short: purpose, quick start, and links to details.
  • Use repository metadata (name, description, language) to populate the draft.
  • Review generated text for voice and project-specific accuracy before committing.
  • Automate the check in pre-merge pipelines but require manual approval for content changes.
  • Provide links from Level 1 to Level 2+ sections rather than duplicating content.

Example use cases

  • A new Python standards repo is created and needs a single-paragraph Level 1 overview for immediate publishing.
  • A CI job flags missing Level 1 headings across dozens of repos; the skill generates drafts for maintainers to review.
  • A team converting internal notes into a formal standards repo uses the skill to scaffold the top-level section.
  • A release checklist requires a minimal Level 1 summary; the skill produces one-liners that describe purpose and start time.

FAQ

Will this skill modify files automatically?

It can generate a draft and optionally apply the change; prefer manual review before committing automated edits.

What content does the generated Level 1 include?

A short purpose statement, scope, recommended quick start, and links to deeper sections derived from available metadata.