algo-complexity-analyzer
Skill3 starsChanged 3 months agoNo licenceView on GitHub
Activate this skill whenever a user asks to reason about the asymptotic time or space complexity of a specific function, snippet, algorithm, or diff. Trigger on exact phrasings such as: "what's the complexity of this function", "is this O(n) or O(n^2)", "will this TLE on N=10^6", "why am I getting Time Limit Exceeded", "can this brute force pass within the time limit", "how do I make this loop faster", "does this recursion blow up", "is there a hidden O(n) inside this loop", "is there a faster algorithm for this", "big-O this code", "how many operations does this do", "will this scale to a million rows", and "review this PR for performance regressions before merge". Also trigger on symptom signatures surfaced by judges/CI/profilers: a "TLE verdict", "MLE verdict", "exceeded time limit", a profiler flagging a hot nested loop, or a code-review comment asking for a Big-O justification. Use during static code review (reading a function/diff without running it) AND during empirical triage (a solution is slow in production or on a judge and the root cause asymptotic class needs to be confirmed by benchmarking, not guessed).
- Installs packages
In this repository59 other files it gives its agents.
- ai-prompt-evaluatorSkill
- ai-rag-pipeline-architectSkill
- algo-edge-case-generatorSkill
- algo-plagiarism-detectorSkill
- algo-stress-testingSkill
- api-mock-generatorSkill
- backend-rest-api-designSkill
- campus-assignment-cleanerSkill
- campus-dsa-visualizerSkill
- campus-fyp-architectureSkill
- campus-git-team-workflowSkill
- campus-hackathon-fast-scaffoldSkill
- campus-ieee-citationSkill
- campus-lab-report-generatorSkill
- campus-presentation-scriptSkill
- ci-workflow-architectSkill
- database-migration-guardianSkill
- db-architectSkill
- devops-dockerfile-optimizerSkill
- devops-vercel-render-deploySkill
- docs-broken-link-checkerSkill
- env-syncSkill
- frontend-clean-uiSkill
- port-inspectorSkill
- react-state-architectureSkill
- repo-doctorSkill
- security-auditorSkill
- test-e2e-playwrightSkill
- test-unit-generatorSkill
- ai-prompt-evaluatorSkill
- ai-rag-pipeline-architectSkill
- algo-complexity-analyzerSkill
- algo-edge-case-generatorSkill
- algo-plagiarism-detectorSkill
- algo-stress-testingSkill
- api-mock-generatorSkill
- backend-rest-api-designSkill
- campus-assignment-cleanerSkill
- campus-dsa-visualizerSkill
- campus-fyp-architectureSkill
- campus-git-team-workflowSkill
- campus-hackathon-fast-scaffoldSkill
- campus-ieee-citationSkill
- campus-lab-report-generatorSkill
- campus-presentation-scriptSkill
- ci-workflow-architectSkill
- database-migration-guardianSkill
- db-architectSkill
- devops-dockerfile-optimizerSkill
- devops-vercel-render-deploySkill
- docs-broken-link-checkerSkill
- env-syncSkill
- frontend-clean-uiSkill
- port-inspectorSkill
- react-state-architectureSkill
- repo-doctorSkill
- security-auditorSkill
- test-e2e-playwrightSkill
- test-unit-generatorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

