github-project-setup
Github Project Setup - Auto-activating skill for Enterprise Workflows. Triggers on: github project setup, github project setup Part of the Enterprise Workflows skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill github-project-setupActivation
7%This description is severely underdeveloped, functioning more as a title than a useful description. It provides no concrete actions, has redundant and limited trigger terms, and lacks any meaningful guidance for when Claude should select this skill. The 'Enterprise Workflows' category mention adds no actionable information.
Suggestions
Add specific concrete actions this skill performs, e.g., 'Creates GitHub repositories, configures branch protection rules, sets up issue templates, initializes project boards, and configures team permissions.'
Add a proper 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to create a new GitHub repository, set up a project from scratch, configure repository settings, or initialize enterprise GitHub workflows.'
Expand trigger terms to include natural variations users would say: 'github repo', 'create repository', 'new project on github', 'initialize git repo', 'github setup', 'repo configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Github Project Setup' without describing any concrete actions. There are no specific capabilities listed like creating repos, configuring settings, or setting up workflows. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is not a proper 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('github project setup' listed twice) and very limited. Missing natural variations users might say like 'create github repo', 'initialize repository', 'set up git project', or 'new github repository'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Github Project Setup' is somewhat specific to GitHub, it could overlap with general git skills, repository management skills, or CI/CD setup skills. The lack of specific actions makes boundaries unclear. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual instructional content. It describes what a GitHub project setup skill would do without providing any concrete guidance, code examples, configuration templates, or actionable steps. The entire content is meta-description that wastes tokens explaining the skill's existence rather than teaching Claude how to perform the task.
Suggestions
Replace the meta-description with actual GitHub project setup steps: repository creation, branch protection rules, required status checks, CODEOWNERS file setup, issue/PR templates
Add executable code examples using GitHub CLI (gh) commands or API calls for common setup tasks
Include a concrete workflow with validation checkpoints, e.g., '1. Create repo with gh repo create, 2. Configure branch protection, 3. Verify settings with gh api'
Remove the 'Capabilities' and 'Example Triggers' sections entirely - they provide no value and waste tokens on information Claude doesn't need
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague filler that Claude doesn't need to be told. | 1 / 3 |
Actionability | There is zero concrete guidance, no code, no commands, no specific steps. The entire skill describes what it claims to do rather than actually instructing how to do anything related to GitHub project setup. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for setting up a GitHub project. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual implementation details, references, or related documentation. There's nothing to disclose progressively because there's no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
Is this your skill?
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.