CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

detect-project

Analyze a project folder or GitHub repository to detect programming language, framework, and version requirements. Use this skill when containerizing an application, selecting an S2I builder image, deploying to OpenShift or RHEL, or determining a project's tech stack. Supports Node.js, Python, Java, Go, Ruby, .NET, PHP, and Perl. Triggers on /detect-project command or when user needs build strategy recommendations. Run before /s2i-build or /rhel-deploy.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is a lean, highly actionable detection workflow with explicit human-in-the-loop checkpoints and concrete tool-level instructions. Its main defect is bundle hygiene: two of four reference files are empty pointer stubs whose cross-skill paths do not resolve, leaving critical checkpoint guidance effectively missing from the bundle.

Suggestions

Fix the dead pointer references: references/human-in-the-loop.md and references/prerequisites.md contain only paths to ../../validate-environment/references/ that do not resolve within this bundle — either inline the mandatory checkpoint behavior and required tools into SKILL.md or make the referenced files resolve to real content.

Add a no-match fallback in Step 2 for when none of the indicator files are found (e.g., ask the user to identify the language or inspect source files directly) to close the workflow gap.

Reconcile the Step 2 heading "(Local Only)" with Scenario B's instruction to "proceed with analysis as if local files" when analyzing a remote repository.

DimensionReasoningScore

Conciseness

The body is efficient: indicator-file, version, and framework detection are compact tables of operational facts with no explanations of concepts Claude already knows. Minor trim opportunities exist — the two multi-block response templates ("Analyzing Remote Repository", "Remote Repository Access") spell out prose Claude could generate itself — so it sits at 4 rather than the lean 5 anchor.

4 / 5

Actionability

Fully concrete, executable guidance throughout: exact MCP calls with parameters ("mcp_github_get_file_contents(owner, repo, path='/')"), URI formats with examples, file-to-language indicator tables, per-language version extraction locations (engines.node, python_requires, go directive), ordered Python entry-point precedence, and a copy-paste-ready findings template. Per the rubric's instruction-skill note, the absence of code is not penalized since the guidance is specific and actionable.

5 / 5

Workflow Clarity

Clear sequenced workflow (Steps 1–5 with scenario branching) and explicit validation checkpoints — two "WAIT for user confirmation" gates plus a correction feedback loop ("If user provides corrections → Update values and show again for confirmation"). Minor gaps keep it below 5: no handling for the no-match case where none of the indicator files are found, and Step 2 is labeled "(Local Only)" while Scenario B says to "proceed with analysis as if local files" for remote repos.

4 / 5

Progressive Disclosure

Structure is good — bulk detail (image mappings) is correctly externalized to references/builder-images.md and python-s2i-entrypoints.md with clear one-level-deep, purpose-labeled links — but two of the four bundle references (human-in-the-loop.md and prerequisites.md) contain only relative pointer paths ("../../validate-environment/references/...") that resolve to nothing, and the body delegates "mandatory checkpoint behavior" to one of these dead links. Clearly signaled but partially broken navigation fits the 3 anchor (could be better organized) rather than 4 (mostly clear references), and is well above 2 since the main content is appropriately split.

3 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

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

A strong description that concretely states what the skill does, when to use it, supported languages, and its position in the deployment skill chain. Trigger terms are natural and domain-specific; the only weaknesses are minor overlap with sibling skills and some missing synonyms for maximal trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — "detect programming language, framework, and version requirements", "selecting an S2I builder image", "determining a project's tech stack" — plus an explicit supported-language list. Falls short of a 5 because the actions revolve around a single composite detection task and it never states what the skill outputs (e.g., builder image recommendation details).

4 / 5

Completeness

Explicitly answers both questions with concrete trigger phrasing: what — "Analyze a project folder or GitHub repository to detect programming language, framework, and version requirements"; when — "Use this skill when containerizing an application, selecting an S2I builder image, deploying to OpenShift or RHEL, or determining a project's tech stack", plus the explicit /detect-project command trigger and ordering ("Run before /s2i-build or /rhel-deploy"). Clearly matches the top anchor, not the 4 anchor where 'when' would be less explicit.

5 / 5

Trigger Term Quality

Strong natural keyword coverage: "containerizing an application", "S2I builder image", "OpenShift", "RHEL", "tech stack", "build strategy", plus eight language names. Not a 5 because common synonyms and file-level triggers users might say (Dockerfile/Containerfile, Kubernetes, "what framework does this repo use") are absent.

4 / 5

Distinctiveness Conflict Risk

Clear S2I/OpenShift/RHEL containerization niche with distinct domain triggers, but "when user needs build strategy recommendations" and the explicit "Run before /s2i-build or /rhel-deploy" create minor overlap risk with the closely related /recommend-image and /s2i-build skills. Mostly distinct rather than fully minimal-conflict, so not a 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-developer/skills/detect-project/SKILL.md

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.