project-catalog
SolidFull project catalog — project paths, stacks, remotes, and runtime paths. Load when you need a project's path, remote, stack, or build/deploy specifics.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- ek33450505
- Repository
- ek33450505/claude-agent-team
- Created
- 5 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
stack-reference
Full tech stack reference and dev command cheatsheet. Load when you need to look up exact package names, commands, or project paths.
tools-catalog
Use to browse, research and install the project's referenced external tools from one unified catalog that merges the knowledge registry (references) with the installable toolkit presets. Install one tool or all missing installables at once, kind-aware (skill-clone preserves LICENSE; a plugin surfaces its own install command, never cherry-picked). The discoverability surface at the intersection of knowledge-ops and skills-ops. Triggers — "/tools", "navega las herramientas referenciadas", "instala esta herramienta", "instálalas todas", "qué herramientas hay para instalar".
project-portfolio
Use this skill when the user is thinking about their work across many projects at once, over time, rather than the single repo or file in front of them. Trigger it when they ask where things stand across everything they're juggling, what to focus on or do next, or for a weekly/periodic review of what's in flight or gone stale; when they want to start keeping track of ongoing efforts scattered across folders (side projects, a job hunt, open pull requests, writing, personal goals) so they stop losing the thread; when they check whether anything changed since they last synced or need to respond to; when they report progress on a weeks-or-months-long effort; or when they wrap up a session and say to log, save, or remember where they left off. This is a persistent, cross-session tracker for long-lived work — not for planning a single task, one-repo status, or one-off questions about the current codebase.