← ClaudeAtlas

coordinate-github-repositorieslisted

Coordinate GitHub repositories across personal accounts and organizations while preserving goals, authority, privacy, workspace roles, and existing workflows. Use for access diagnosis, inventory, findability, portfolio understanding, repository routing, cross-repository work, practice reuse, functionality and knowledge reuse, tool comparison, initial orientation, installation and updates of this skill, or an explicit language quality review of coordination output generated by this skill. Supports software, documentation, writing, research, data, operations, and mixed work. Do not use as the primary workflow for routine work in one known repository or blanket destructive execution inferred only from inactivity; require lifecycle evidence.
TechSpokes/skill-github-repositories-coordination · ★ 0 · Code & Development · score 63
Install: claude install-skill TechSpokes/skill-github-repositories-coordination
# Coordinate GitHub Repositories ## Goal Help the user and their agents preserve and reuse repository-centered value with less human administration, without imposing a taxonomy, tool, or replacement workflow. Work with the capabilities available in the current agent, remain useful with conversation alone, and keep every immediate task connected to the user's intended benefit. ## Read Depth Read the Goal and Must-Follow Rules for every run. Follow the workflow and load a direct reference only when its stage names the applicable condition. Load [goal and authority](references/goal-and-authority.md) when work crosses repositories or workspaces, survives a summary or handoff, changes materially, contains a goal conflict, or raises an artifact placement question. If context limits prevent reading an applicable safety reference, remain advisory and do not mutate access, repositories, organization state, durable records, or public output. Load [writing quality](references/writing-quality.md) only when the user requests a language quality pass on coordination output or generated files, reports a concrete clarity defect, or asks for a final language review before handoff or publication. ## Must-Follow Rules - Preserve applicable organization and repository instructions. - Detect capabilities and access. Do not assume a shell, IDE, connector, MCP server, GitHub write access, or administrative authority. - Do not interpret a broad outcome as blanket mutation or publication autho