swing-research
Deep research with cross-verification and source tiering. Use when investigating technologies, comparing tools, fact-checking claims, evaluating architectures, or any task requiring verified information. Triggers on "조사해줘", "리서치", "research", "investigate", "fact-check", "비교 분석", "검증해줘".
npx skills add majiayu000/claude-skill-registry --skill swing-research-thestack-ai-swing-skills --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.
# Cross-Verified Research Systematic research engine with anti-hallucination safeguards and source quality tiering. ## Rules (Absolute) 1. **Never fabricate sources.** No fake URLs, no invented papers, no hallucinated statistics. 2. **Source-traceability gate.** Every factual claim must be traceable to a specific, citable source. If a claim cannot be traced to any source, mark it as **Unverified (internal knowledge only)** and state what verification would be needed. Never present untraced claims as findings. 3. **No speculation as fact.** Do not present unverified claims using hedging language as if they were findings. Banned patterns: "아마도", "~인 것 같습니다", "~로 보입니다", "~수도 있습니다", "probably", "I think", "seems like", "appears to be", "likely". If a claim is not verified, label it explicitly as **Unverified** or **Contested** — do not soften it with hedging. 4. **BLUF output.** Lead with conclusion, follow with evidence. Never bury the answer. 5. **Scaled effort.** Match research depth to question scope: - **Narrow factual** (single claim, date, specification): 2-3 queries, 2+ sources - **Technology comparison** (A vs B): 5+ queries, 5+ sources - **Broad landscape** (market analysis,
- Rules (Absolute)
- Pipeline
- Stage 1: Deconstruct
- Stage 2: Search & Collect
- Stage 3: Cross-Verify
- Stage 4: Synthesize
- Output Format
- Quality Calibration
- BAD Example — What to Avoid
- GOOD Example — What to Aim For
- Source Tiers
- Tier Classification Rules
- When to Use
- When NOT to Use
What does the swing-research skill do?
Deep research with cross-verification and source tiering. Use when investigating technologies, comparing tools, fact-checking claims, evaluating architectures, or any task requiring verified information. Triggers on "조사해줘", "리서치", "research", "investigate", "fact-check", "비교 분석", "검증해줘".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill swing-research-thestack-ai-swing-skills --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.