Automated summary
Performs deep maintenance on the OlyBars repo by analyzing code for unused functions and optimizing GCP deployments.
Strengths
- Identifies dead code through static analysis
- Optimizes Cloud Run configurations on GCP
- Produces a clear and actionable Hygiene Report
- Reduces project bloat and complexity
Limitations
- Only works with the OlyBars repository
- Requires running a specific script
- May miss dynamically referenced functions
Use this skill when the user asks to optimize or clean up the OlyBars project.
Do not use it if the project is not OlyBars or if broader code quality improvements are needed.
Security analysis
CautionThe skill uses a shell command to execute a repository script, which falls under powerful tooling. While the intent is legitimate maintenance, the script’s behavior is unverified, so caution is warranted.
- •The skill instructs running a locally-provided TypeScript script via npx, which could perform arbitrary file system operations or network requests. Although the script is intended for static analysis and cleanup, without auditing its contents, there is inherent risk in execution.
Examples
Optimize the OlyBars project and clean up any redundant code.Clean up the site and find any unused functions in the codebase.Run the janitor script to perform a hygiene check on the repository.name: janitor description: Performs deep maintenance on the OlyBars repo. Use this when the user asks to "optimize the project," "clean up the site," or "find redundant code."
Janitor Skill
Goals
- Maintain a lean, high-performance us-west1 GCP footprint.
- Ensure the repository remains readable for other agents in the swarm.
Instructions
- Introspection: Read
ARCHITECTURE.mdand thepackage.jsonto understand the intended stack. - Analysis: Traverse the
src/directory. Use static analysis to find functions with no internal references. - GCP Guardrails: Verify Cloud Run configurations in
server/aren't bundling unnecessary folders (e.g.,tests/ordocs/) into the production container. - Propose: Create a "Hygiene Report" artifact with a checklist of suggested deletions.
Execution
Use the custom script scripts/janitor.ts to perform the heavy lifting of static analysis.
npx tsx scripts/janitor.ts
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/code-janitor-and-optimization-mm5t8boe/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/code-janitor-and-optimization-mm5t8boe' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-janitor-and-optimization-mm5t8boe/download' --output '.skill-downloads/code-janitor-and-optimization-mm5t8boe/SKILL.md.part' && mv '.skill-downloads/code-janitor-and-optimization-mm5t8boe/SKILL.md.part' '.skill-downloads/code-janitor-and-optimization-mm5t8boe/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/code-janitor-and-optimization-mm5t8boe/SKILL.md' && test -s '.skill-downloads/code-janitor-and-optimization-mm5t8boe/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/janitor' && cp -R '.skill-downloads/code-janitor-and-optimization-mm5t8boe' '.claude/skills/janitor'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/code-janitor-and-optimization-mm5t8boe'openskills read 'code-janitor-and-optimization-mm5t8boe'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/code-janitor-and-optimization-mm5t8boe/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.