Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →alinaqi/existing-repo
Analyze existing repositories, maintain structure, setup guardrails and best practices
Passed 19 of 22 test cases with the skill, and 11 of 22 without it.
and 8 more in the full report
9 fixed10 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What bash command should be used to map out top-level repository directories while excluding build artifacts, cache directories, and package installations?
| Checked | Without skill | With skill |
|---|---|---|
| Sets maximum directory search depth to 3 levels | Missed | Passed |
| Excludes node_modules directory from directory listing | Passed | Passed |
The instructions your model reads when the skill loads.
For working with existing codebases - analyze structure, respect conventions, and set up proper guardrails without breaking anything.
Sources: Husky | lint-staged | pre-commit | commitlint
Understand before modifying. Existing repos have conventions, patterns, and history. Your job is to work within them, not reorganize them.
ALWAYS run this analysis first when joining an existing repo.
# Check git status
git remote -v 2>/dev/null
git branch -a 2>/dev/null
git log --oneline -5 2>/dev/null
# Check for existing configs
ls -la .* 2>/dev/null | head -20
ls *.json *.toml *.yaml *.yml 2>/dev/null
# JavaScript/TypeScript
ls package.json tsconfig.json 2>/dev/null
# Python
ls pyproject.toml setup.py requirements*.txt 2>/dev/null
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.