.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/eveld/claude
home/skills/eveld/claude
eveld avatar

eveld/claude

29 skills

View on GitHub
$npx skills add eveld/claude
SkillInstalls
agent-awarenessALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration.—before-code-analysisUse BEFORE reading multiple files to understand code. Reminds you to use codebase-analyzer agent instead of manual file reading.—before-file-searchUse BEFORE running grep or glob commands. Reminds you to use codebase-locator agent instead of basic file search tools.—before-spawning-taskUse BEFORE using the Task tool. Ensures you select the correct specialized subagent_type instead of generic agents.—debug-systematicallyUse when encountering errors or bugs to follow a systematic debugging process instead of jumping to conclusions.—determine-feature-slugDetermine feature slug interactively by auto-detecting next number and prompting user for description—discover-project-commandsUse during planning to discover and document available project commands (make targets, npm scripts, etc.) for success criteria.—discover-test-patternsUse during planning to discover and document test patterns and conventions for writing consistent tests.—follow-test-patternsUse when writing tests to ensure they follow project conventions. References patterns from thoughts/notes/testing.md.—gather-project-metadataUse when creating research or plan documents to gather git commit, branch, repository info.—gcp-awarenessALWAYS check before using gcloud commands. Guide for GCP-related skills and tools.—gcp-logsQuery GCP Cloud Logging for errors, service logs, and request traces. Use when investigating GCP-hosted services.—k8s-awarenessALWAYS check before using kubectl commands. Guide for Kubernetes-related skills.—k8s-debugLaunch ephemeral debug container in running pod for interactive debugging. Use when you need to debug a pod without restarting it.—k8s-queryQuery Kubernetes resources (pods, deployments, services, events). Use when checking cluster state and resource status.—linear-awarenessALWAYS check before working with Linear issues. Guide for Linear-related skills for ticket management and debugging workflows.—linear-issuesFetch and view Linear issues/tickets. List, search, read issue details, status, comments. Use when investigating tickets or gathering debugging context.—linear-updateUpdate Linear issues with debugging findings. Add comments, change status, update labels, set priority. Use after completing investigations.—share-docsShare personal documents to the shared namespace with atomic git commit and push—spawn-implementation-agentsGuide for efficient agent orchestration during implementation to conserve main agent context—spawn-planning-agentsUse when creating implementation plans to research codebase patterns and gather context for planning.—spawn-research-agentsUse when conducting codebase research to orchestrate specialized agents in parallel for comprehensive investigation.—update-changelogAppend phase completion details or final summary to changelog.md during implementation—upgrade-pluginGeneric migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations—verify-implementationUse after implementing changes to run verification commands and ensure tests pass, code builds, and functionality works.—write-commit-messageUse when creating git commits to ensure consistent, clear commit messages following conventional commits format.—write-plan-docUse when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.—write-pr-descriptionUse when creating pull requests to write clear, structured PR descriptions that help reviewers understand changes.—write-research-docUse when documenting research findings to create properly structured research documents with frontmatter, sections, and file references.—