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.

1.00x

Quality

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/github-project-setup/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond the skill name repeated, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of similar skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates GitHub repositories, configures branch protection rules, sets up CI/CD workflows, initializes README and .gitignore files, and configures team permissions.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a new GitHub repo, initialize a project on GitHub, set up repository settings, configure GitHub Actions, or scaffold a new codebase with version control.'

Remove the duplicate trigger term ('github project setup' listed twice) and expand with varied natural phrases users might say, such as 'new repo', 'start a GitHub project', 'repository setup', 'initialize git project'.

Dimension	Reasoning	Score
Specificity	The description only says 'Github Project Setup' without listing any concrete actions. There are no specific capabilities described like creating repos, configuring CI/CD, setting up branch protection, etc.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states the skill name and category without explaining capabilities or explicit trigger conditions.	1 / 3
Trigger Term Quality	The trigger terms are just 'github project setup' repeated twice. Missing natural variations users would say like 'create a repo', 'initialize repository', 'set up GitHub', 'new project on GitHub', '.gitignore', etc.	1 / 3
Distinctiveness Conflict Risk	The description is too vague to distinguish from other project setup, GitHub, or repository management skills. 'Enterprise Workflows' is a generic category label that doesn't help differentiate.	1 / 3
	Total	4 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a placeholder or template with no substantive content. It describes what it would do in abstract terms but provides no actual instructions, code, commands, or workflows for GitHub project setup. It fails on every dimension because it contains no actionable information whatsoever.

Suggestions

Replace the abstract capability descriptions with concrete, executable steps for GitHub project setup (e.g., `gh repo create`, branch protection rules, CI/CD configuration, CODEOWNERS setup).

Add production-ready code examples or configuration files (e.g., `.github/workflows/ci.yml`, `CODEOWNERS`, branch protection API calls) that Claude can directly use.

Define a clear multi-step workflow with validation checkpoints, such as: 1) Create repo, 2) Configure branch protection, 3) Set up CI/CD, 4) Validate settings via `gh api` calls.

If the topic is broad, create a concise overview with links to separate detailed files for specific subtopics (e.g., `CI_SETUP.md`, `BRANCH_PROTECTION.md`, `COMPLIANCE.md`).

Dimension	Reasoning	Score
Conciseness	The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, commands, or configurations. Every section restates the same vague idea.	1 / 3
Actionability	There is zero concrete guidance—no commands, no code, no configuration examples, no specific steps for setting up a GitHub project. Phrases like 'provides step-by-step guidance' and 'generates production-ready code' describe capabilities without demonstrating them.	1 / 3
Workflow Clarity	No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but none is actually present.	1 / 3
Progressive Disclosure	The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured sections with real content, and no navigation to deeper resources.	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: dc559db

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.