Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.
64
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/project-setup/SKILL.mdAdd a new GitHub repository as a tracked project in the workspace and install workflow automation.
Extract owner/repo from the user's message. If ambiguous, ask. Validate via GitHub API: http(method="GET", url="https://api.github.com/repos/{owner}/{repo}"). If 404 or no access, tell the user.
staging if yes)Read main_branch from the API response's default_branch field.
Write projects/<owner>-<repo>/project.md:
---
type: project
repo: <owner/repo>
added_at: <today YYYY-MM-DD>
maintainers: [<handles>]
main_branch: <branch from API>
staging_branch: <branch or null>
ai_agent_authors: [<bot handles>]
workflow_installed: false
---
# <owner/repo>
<description from API response>
## Workflow missions
(populated after install)Write projects/<owner>-<repo>/notes.md:
# Notes: <owner/repo>
Developer notes for this project. Searchable via memory_search.Follow the github-workflow skill's install procedure. For each of the 6 mission templates in github-workflow/references/workflow-routines.md:
{{repository}} with owner/repo{{slug}} with <owner>-<repo>{{maintainers}} with the maintainer list{{main_branch}} and {{staging_branch}} with the configured branches{{batch_interval_hours}} with 8 (default)mission_create(name, goal, cadence) for eachIf staging_branch is null, skip wf-staging-review-<slug>.
After installing, update the project file:
workflow_installed: true## Workflow missionsAdded <owner/repo> as a tracked project:
- Project file: projects/<owner>-<repo>/project.md
- Workflow missions installed: <list>
- Maintainers: <list>
- Main branch: <branch>, Staging: <branch or "none">
- This repo is now included in your morning brief and triage scans
Say "add repo <another/repo>" to add more, or "remove repo <owner/repo>" to uninstall.800b781
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.