tech-research-enforcer
Enforces iterative web research for coding and DevOps questions to prevent assumptions about libraries, frameworks, APIs, versions, and configurations. Use this skill when the user asks about programming languages, frameworks, libraries, DevOps tools, cloud platforms, databases, container orchestration, CI/CD, infrastructure as code, or any technical topic where current documentation, version-specific behavior, or recent changes matter. This skill ensures Claude searches and fetches authoritative sources before answering, even for topics Claude may have knowledge about, to verify current state
npx skills add majiayu000/claude-skill-registry --skill tech-research-enforcer-jayteealao-aperture --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.
# Tech Research Enforcer ## Core Principle **Never assume. Always verify.** Technology changes rapidly—APIs evolve, libraries update, best practices shift, and documentation changes. Even when Claude has knowledge about a topic, that knowledge may be outdated or incomplete for the user's specific context. ## Mandatory Research Workflow ### When to Use This Workflow ALWAYS use this workflow for questions involving: - Programming languages (Python, JavaScript, Go, Rust, Java, C#, etc.) - Frameworks and libraries (React, Vue, Django, FastAPI, Spring Boot, .NET, etc.) - DevOps tools (Docker, Kubernetes, Terraform, Ansible, Helm, etc.) - Cloud platforms (AWS, Azure, GCP, DigitalOcean, etc.) - Databases (PostgreSQL, MySQL, MongoDB, Redis, etc.) - Build tools and package managers (npm, pip, cargo, Maven, Gradle, etc.) - CI/CD platforms (GitHub Actions, GitLab CI, Jenkins, CircleCI, etc.) - Monitoring and observability (Prometheus, Grafana, ELK, Datadog, etc.) - Infrastructure as Code (Terraform, Pulumi, CloudFormation, etc.) - Container orchestration (Kubernetes, Docker Swarm, ECS, etc.) ### Step 1: Identify What Needs Verification Before answering any technical question, explicitly ident
- Core Principle
- Mandatory Research Workflow
- When to Use This Workflow
- Step 1: Identify What Needs Verification
- Step 2: Search for Current Information
- Step 3: Fetch and Read Official Documentation
- Step 4: Verify and Cross-Reference
- Step 5: Iterate If Needed
- Response Guidelines
- Always Include
- Format for Technical Responses
- Never Do
- Special Cases
- Library/Framework Comparisons
What does the tech-research-enforcer skill do?
Enforces iterative web research for coding and DevOps questions to prevent assumptions about libraries, frameworks, APIs, versions, and configurations. Use this skill when the user asks about programming languages, frameworks, libraries, DevOps tools, cloud platforms, databases, container orchestration, CI/CD, infrastructure as code, or any technical topic where current documentation, version-specific behavior, or recent changes matter. This skill ensures Claude searches and fetches authoritative sources before answering, even for topics Claude may have knowledge about, to verify current state
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill tech-research-enforcer-jayteealao-aperture --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.