workflow-onboarding

Name: workflow-onboarding
Availability: InStock
Author: dividedby

Configure GitHub repository labels and capability documentation for proposal-loop workflows.

1|2|Updated May 27, 2026

Search Tags:#automation #workflow #onboarding #github #agent #labels

Ready to run

npx skills add https://github.com/dividedby/skills --skill workflow-onboarding

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-onboarding
Source: https://github.com/dividedby/skills/tree/main/skills/config/workflow-onboarding
Command: npx skills add https://github.com/dividedby/skills --skill workflow-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the inconsistency and manual overhead of configuring new repositories for automated proposal-loop workflows, ensuring all required labels and documentation are correctly initialized.

Core Features & Use Cases

Automated Labeling: Idempotently creates or updates the six canonical LOOP/NETWORK labels required for agent-driven proposal loops.
Documentation Seeding: Automatically generates the docs/agents/installed-skills.md file to expose repository capabilities to remote agents.
Safety Guardrails: Enforces a mandatory human-in-the-loop confirmation step before any network mutations or file writes occur.

Quick Start

Run the workflow-onboarding skill to initialize the required labels and documentation for the current repository.

Frequently Asked Questions about workflow-onboarding

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

FAQPage Schema

How do I automate GitHub repository onboarding for proposal loop workflows?▼

You can automate repository setup by running a skill that synchronizes mandatory labels and generates capability documentation. This idempotently creates the six canonical LOOP/NETWORK labels and seeds the installed-skills markdown file to ensure consistent agent-to-repo communication.

Why do I need to synchronize canonical labels for automated agent workflows?▼

Synchronizing canonical labels provides consistent triage surfaces for remote agents operating within the repository. Without the mandatory LOOP/NETWORK labels, automated proposal-loop workflows cannot properly categorize and route agent-driven interactions.

Do I need the GitHub CLI to configure repository infrastructure for proposal loops?▼

Yes, the GitHub CLI is required to configure repository infrastructure for proposal loops. The onboarding process relies on the CLI to execute network mutations, create mandatory labels, and enforce the mandatory human-in-the-loop safety guardrails.

Can I use workflow-onboarding to generate capability documentation for remote agents?▼

Yes, you can generate capability documentation by running the workflow-onboarding skill, which automatically creates the docs/agents/installed-skills.md file. This file explicitly exposes repository capabilities to remote agents, enabling proper agent-to-repo communication.

What safety guardrails are enforced when synchronizing repository labels?▼

The label synchronization process enforces a mandatory human-in-the-loop confirmation step before executing any network mutations or file writes. This guardrail prevents unauthorized or unintended changes to the repository infrastructure during the onboarding process.

Is the repository label synchronization process idempotent?▼

Yes, the repository label synchronization process is idempotent, safely creating or updating the six canonical LOOP/NETWORK labels without duplicating entries. Running the workflow-onboarding skill multiple times maintains repository consistency without causing label conflicts.