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 gives no guidance on when Claude should select it. It would be nearly indistinguishable from any other GitHub or project setup skill.

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.'

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, set up GitHub Actions, or configure repository settings.'

Remove the duplicate trigger term 'github project setup' and replace with diverse natural language variations users would actually say, such as 'new repo', 'create repository', 'set up GitHub project', 'initialize 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 enterprise workflow skills. 'Enterprise Workflows' is a broad 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 a hollow placeholder with no substantive content. It consists entirely of meta-descriptions about what the skill supposedly does without providing any actual instructions, code, commands, or configurations for GitHub project setup. It fails on every dimension because it contains no actionable information whatsoever.

Suggestions

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

Add actual code/command examples such as `gh repo create`, `.github/` directory templates, workflow YAML files, and branch protection API calls.

Define a clear workflow sequence with validation checkpoints, e.g., 1. Create repo → 2. Configure branch protection → 3. Validate settings → 4. Set up CI/CD → 5. Verify pipeline runs.

If the skill covers multiple sub-topics (repo setup, CI/CD, compliance, governance), create separate reference files and link to them from a concise overview in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, commands, or configurations. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding.	1 / 3
Actionability	There is zero concrete, executable guidance. No commands, no code, no configuration examples, no actual steps for setting up a GitHub project. The entire content describes rather than instructs.	1 / 3
Workflow Clarity	No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for any project setup process.	1 / 3
Progressive Disclosure	There are no references to supporting files, no structured navigation, and no bundle files. The content is a monolithic block of vague descriptions with no layered information architecture.	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: 3a2d27d

Reviewed: 2 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.