component-research
This skill should be used when the user asks to "evaluate if TBC covers a use case", "decide which TBC component to use", "check if a TBC template fits", "research TBC capabilities", "find the right TBC template", "analyze if custom step is needed", "compare TBC templates", or needs to determine whether To-Be-Continuous framework components can solve a CI/CD requirement before generating configuration.
npx skills add majiayu000/claude-skill-registry --skill component-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# TBC Component Research Process for determining if a To-Be-Continuous (TBC) component fits a use case or requires customization. ## Flow Research → Evaluate → AskUserQuestion → User selects → Proceed ## Purpose This skill provides a systematic research process to evaluate TBC framework capabilities against user requirements. Use this BEFORE generating any configuration to ensure the correct solution path. ## When to Use - Before generating `.gitlab-ci.yml` with TBC - When user requests functionality that may or may not be covered by TBC - When deciding between TBC template, variant, or custom solution - When user asks for something and the approach needs validation ## Solution Priority Hierarchy **ALWAYS follow this priority order. Higher priority = preferred solution.** | Priority | Solution | When to Use | |----------|----------|-------------| | 1 (Highest) | TBC template direct | Template inputs cover use case 100% | | 2 | Template + existing variant | Template needs authentication/secrets variant | | 3 | Variant from other template | Another template has variant that fits | | 4 | New component | Create new TBC template | | 5 | New component + variant | Create new template with
- Flow
- Purpose
- When to Use
- Solution Priority Hierarchy
- Decision Process Overview
- Quick Decision Steps
- Step 1: Identify Core Need
- Step 2: Search Template Catalog
- Step 3: Evaluate Template Fit
- Step 4: Deep Research (If Partial Match)
- Step 5: Present Options to User
- Output Format
- Reference Files
- Integration with building-with-tbc
What does the component-research skill do?
This skill should be used when the user asks to "evaluate if TBC covers a use case", "decide which TBC component to use", "check if a TBC template fits", "research TBC capabilities", "find the right TBC template", "analyze if custom step is needed", "compare TBC templates", or needs to determine whether To-Be-Continuous framework components can solve a CI/CD requirement before generating configuration.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill component-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.