One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill best-practice-research-shayne-snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: best-practice-research
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/best-practice-research
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill best-practice-research-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from relying on outdated or memory-based advice by producing a reusable, evidence-backed best-practice answer that clearly separates upstream facts from repo-local decisions.

Core Features & Use Cases

  • Upstream-first best-practice synthesis: Prioritizes official documentation, release notes, standards, and maintainer guidance with source URLs.
  • Version- and date-aware guidance: Adds version/date context and flags stale, conflicting, or version-mismatched evidence.
  • Repo-local constraint integration: Optionally pulls bounded local facts via targeted repo exploration before finalizing recommendations.
  • Handoff-oriented output: Returns recommendations, evidence, uncertainty, and explicit boundaries so planning or execution can proceed safely.

Example use case: You’re preparing an implementation plan for a specific technology and need current official migration guidance before choosing an approach.

Quick Start

Ask for evidence-grounded, version-aware best practices for your chosen technology, including a clear implementation-oriented handoff.

Frequently Asked Questions about best-practice-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find official best practices and migration guidance for a specific technology version?

Best practice research generates evidence-backed recommendations by prioritizing upstream official documentation, release notes, and maintainer guidance with cited URLs. It explicitly flags stale, conflicting, or version-mismatched evidence to ensure migration guidance remains current.

How do I get version-aware recommendations that fit my repository's local constraints?

Version-aware recommendations integrate repo-local constraints by gathering bounded local facts through targeted repository exploration before finalizing advice. This ensures synthesized upstream best practices directly align with your specific codebase configuration and architectural decisions.

Can I use upstream evidence to plan a technology migration without making dependency adoption decisions?

Yes, upstream evidence supports migration planning by establishing clear boundaries that explicitly avoid making dependency adoption decisions. It provides handoff-oriented output that separates upstream facts from repo-local decisions, enabling safe execution and technology approach selection.

What is the best way to separate official upstream facts from local decisions during research synthesis?

The best way to separate upstream facts from local decisions is through handoff-oriented research synthesis that returns distinct recommendations, cited evidence, and uncertainty boundaries. This prevents teams from relying on outdated or memory-based advice during execution planning.

When should I not rely on memory-based advice for current technology best practices?

You should not rely on memory-based advice when tasks require current, version-aware recommendations for already-chosen technologies. Memory-based advice lacks the explicit version, date context, and upstream citations needed to flag stale or conflicting evidence correctly.