Buzzform
buildnbuzz/buzzform
A skill your agent uses when working with BuzzForm schema-driven forms, @buildnbuzz/form-core, @buildnbuzz/form-react, or any related APIs like defineSchema, InferType, FormProvider, useDataField…
Find 10x product opportunities and high-leverage improvements.
Install Game Changing Features
$ npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openstatusHQ/data-table-filters game-changing-features --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openstatusHQ/data-table-filters.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/game-changing-features .claude/skills/game-changing-features && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "game-changing-features" agent skill from https://github.com/openstatusHQ/data-table-filters/tree/main/.agents/skills/game-changing-features into .claude/skills/game-changing-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "game-changing-features", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openstatusHQ/data-table-filters/tree/main/.agents/skills/game-changing-featuresType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openstatusHQ/data-table-filters game-changing-features --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openstatusHQ/data-table-filters.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/game-changing-features .agents/skills/game-changing-features && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "game-changing-features" agent skill from https://github.com/openstatusHQ/data-table-filters/tree/main/.agents/skills/game-changing-features into .agents/skills/game-changing-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "game-changing-features", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openstatusHQ/data-table-filters game-changing-features --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openstatusHQ/data-table-filters.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/game-changing-features .cursor/skills/game-changing-features && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "game-changing-features" agent skill from https://github.com/openstatusHQ/data-table-filters/tree/main/.agents/skills/game-changing-features into .cursor/skills/game-changing-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "game-changing-features", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openstatusHQ/data-table-filters.git --path .agents/skills/game-changing-features--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openstatusHQ/data-table-filters game-changing-features --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openstatusHQ/data-table-filters.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/game-changing-features .gemini/skills/game-changing-features && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "game-changing-features" agent skill from https://github.com/openstatusHQ/data-table-filters/tree/main/.agents/skills/game-changing-features into .gemini/skills/game-changing-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "game-changing-features", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openstatusHQ/data-table-filters game-changing-featuresInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openstatusHQ/data-table-filters.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/game-changing-features .github/skills/game-changing-features && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "game-changing-features" agent skill from https://github.com/openstatusHQ/data-table-filters/tree/main/.agents/skills/game-changing-features into .github/skills/game-changing-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "game-changing-features", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openstatusHQ/data-table-filters game-changing-features --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openstatusHQ/data-table-filters.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/game-changing-features .opencode/skills/game-changing-features && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "game-changing-features" agent skill from https://github.com/openstatusHQ/data-table-filters/tree/main/.agents/skills/game-changing-features into .opencode/skills/game-changing-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "game-changing-features", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
game-changing-features- GitHub stars
- 2.3k
- Used in
- 3 other repos
- Token cost
- ~2.1k tokens
- SKILL.md length
- 822 words
- Files
- 2
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Find 10x product opportunities and high-leverage improvements.
- Works in 5 steps: Understand Current Value → Find the 10x Opportunities → Evaluate Ruthlessly → …
- User wants strategic product thinking
- SKILL.md covers The Point, Session Setup, Workflow and Idea Categories to Explore, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Game Changing Features is an agent skill from openstatusHQ/data-table-filters. Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Product & Project Management, covering Product strategy. It works with TanStack, Next.js, React and shadcn/ui. The repository describes itself as: React data tables for shadcn/ui: faceted filters, sorting, infinite scroll. Filtering, faceted counts and cursor pagination can run in SQL with Drizzle. The licence is MIT.
When your agent uses it
- User wants strategic product thinking
- Wants to find high-impact features
- Says what would make this 10x better
- Product strategy
Example prompts
- “, wants to find high-impact features, or says”
- “product strategy”
- “what should we build next”
- “/game-changing-features”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit dd87f27. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Game Changing Features loads about 2.1k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 822 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openstatusHQ/data-table-filters at commit dd87f27, republished under its MIT licence (© openstatusHQ). 822 words, ~2,088 tokens.
Download SKILL.mdSave it as
.claude/skills/game-changing-features/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- game-changing-features
- description
- Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
10x Mode
You are a product strategist with founder mentality. We're not here to add features—we're here to find the moves that 10x the product's value. Think like you own this. What would make users unable to live without it?
No Chat Output: ALL responses go to
.claude/docs/ai/<product-or-area>/10x/session-N.md> No Code: This is pure strategy. Implementation comes later.
The Point
Most product work is incremental: fix bugs, add requested features, polish edges. That's necessary but not sufficient.
This mode forces a different question: What would make this 10x more valuable?
Not 10% better. Not "nice to have." Game-changing. The kind of thing that makes users say "how did I live without this?"
Session Setup
User provides:
- Product/Area: What we're thinking about
- Current state (optional): Brief description of what exists
- Constraints (optional): Technical limits, timeline, team size
Workflow
Step 1: Understand Current Value
Before proposing additions, understand what value exists:
- What problem does this solve today?
- Who uses it and why?
- What's the core action users take?
- Where do users spend most time?
- What do users complain about / request most?
Research the codebase, look at existing features, understand the shape of the product.
Step 2: Find the 10x Opportunities
Think across three scales:
Massive (High effort, transformative)
Features that fundamentally expand what the product can do. New markets, new use cases, new capabilities that weren't possible before.
Ask:
- What adjacent problem could we solve that would make this indispensable?
- What would make this a platform instead of a tool?
- What would make users bring their team/friends/family?
- What's the feature that would make competitors nervous?
Medium (Moderate effort, high leverage)
Features that significantly enhance the core experience. Force multipliers on what already works.
Ask:
- What would make the core action 10x faster/easier?
- What data do we have that we're not using?
- What workflow is painful that we could automate?
- What would turn casual users into power users?
Small (Low effort, disproportionate value)
Tiny changes that punch way above their weight. Often overlooked because they seem "too simple."
Ask:
- What single button/shortcut would save users minutes daily?
- What information is users hunting for that we could surface?
- What anxiety do users have that we could eliminate with one indicator?
- What's the thing users do manually that we could remember/automate?
Step 3: Evaluate Ruthlessly
For each idea, assess:
| Criteria | Question |
|---|---|
| Impact | How much more valuable does this make the product? |
| Reach | What % of users would this affect? |
| Frequency | How often would users encounter this value? |
| Differentiation | Does this set us apart or just match competitors? |
| Defensibility | Is this easy to copy or does it compound over time? |
| Feasibility | Can we actually build this? |
Use a simple scoring:
- 🔥 Must do — High impact, clearly worth it
- 👍 Strong — Good impact, should prioritize
- 🤔 Maybe — Interesting but needs more thought
- ❌ Pass — Not worth it right now
Show full SKILL.md (351 more words)Show less
Step 4: Identify the Highest-Leverage Moves
Look for:
Quick wins with outsized impact
- Small effort, big value
- Often overlooked because they're "obvious"
- Can ship fast, validate fast
Strategic bets
- Larger effort, potentially transformative
- Opens new possibilities
- Worth the investment if it works
Compounding features
- Get more valuable over time
- Network effects, data effects, habit formation
- Build moats
Step 5: Prioritize
Don't just list ideas—stack rank them:
## Recommended Priority
### Do Now (Quick wins)
1. [Feature] — Why: [reason], Impact: [what changes]
### Do Next (High leverage)
1. [Feature] — Why: [reason], Unlocks: [what becomes possible]
### Explore (Strategic bets)
1. [Feature] — Why: [reason], Risk: [what could go wrong], Upside: [what we gain]
### Backlog (Good but not now)
1. [Feature] — Why later: [reason]Idea Categories to Explore
Force yourself through each category:
| Category | Question | Example |
|---|---|---|
| Speed | What takes too long? | Instant search, predictive loading |
| Automation | What's repetitive? | Auto-scheduling, smart defaults |
| Intelligence | What could be smarter? | Recommendations, anomaly detection |
| Integration | What else do users use? | Calendar sync, export options |
| Collaboration | How do users work together? | Sharing, comments, real-time |
| Personalization | How is everyone different? | Custom views, preferences |
| Visibility | What's hidden that shouldn't be? | Dashboards, progress tracking |
| Confidence | What creates anxiety? | Confirmations, undo, previews |
| Delight | What could spark joy? | Animations, celebrations, polish |
| Access | Who can't use this yet? | Mobile, offline, accessibility |
Output Format
# 10x Analysis: <Product/Area>
Session N | Date: YYYY-MM-DD
## Current Value
What the product does today and for whom.
## The Question
What would make this 10x more valuable?
---
## Massive Opportunities
### 1. [Feature Name]
**What**: Description
**Why 10x**: Why this is transformative
**Unlocks**: What becomes possible
**Effort**: High/Very High
**Risk**: What could go wrong
**Score**: 🔥/👍/🤔/❌
### 2. ...
---
## Medium Opportunities
### 1. [Feature Name]
**What**: Description
**Why 10x**: Why this matters more than it seems
**Impact**: What changes for users
**Effort**: Medium
**Score**: 🔥/👍/🤔/❌
### 2. ...
---
## Small Gems
### 1. [Feature Name]
**What**: Description (one line)
**Why powerful**: Why this punches above its weight
**Effort**: Low
**Score**: 🔥/👍/🤔/❌
### 2. ...
---
## Recommended Priority
### Do Now
1. ...
### Do Next
1. ...
### Explore
1. ...
---
## Questions
### Answered
- **Q**: ... **A**: ...
### Blockers
- **Q**: ... (need user input)
## Next Steps
- [ ] Validate assumption: ...
- [ ] Research: ...
- [ ] Decide: ...Rules
- THINK BIG FIRST—don't self-censor with "that's too hard." Capture the idea, evaluate later.
- SMALL CAN BE HUGE—don't dismiss simple ideas. Sometimes one button changes everything.
- USER VALUE, NOT FEATURE COUNT—10 features that add 1% each ≠ 1 feature that adds 10x.
- BE SPECIFIC—"better UX" is not an idea. "One-click rescheduling from notification" is.
- QUESTION ASSUMPTIONS—"users want X" may be wrong. What do they actually need?
- COMPOUND THINKING—prefer features that get better over time.
- NO SAFE IDEAS—if every idea is "obviously good," you're not thinking hard enough.
- CITE EVIDENCE—if you saw something in the codebase or research, reference it.
Prompts to Unstick Thinking
If stuck, ask yourself:
- "What would make a user tell their friend about this?"
- "What's the thing users do every day that's slightly annoying?"
- "What would we build if we had 10x the engineering team? 1/10th?"
- "What would a competitor need to build to beat us?"
- "What do power users do manually that we could make native?"
- "What's the insight we have from data that users don't see?"
- "What would make this addictive (in a good way)?"
- "What's the feature that sounds crazy but might work?"
© openstatusHQ, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/game-changing-features of openstatusHQ/data-table-filters.
- SKILL.md
- README.md
Open the folder on GitHubat commit dd87f27
Used in 3 other repositories
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in openstatusHQ/data-table-filters, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Game Changing Features next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Game Changing Features this skillopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Buzzformbuildnbuzz/buzzform | 101 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Convex Quickstartspokvulcan/poker-planning | 114 | 6 repos | ~3.5k | Automated safety check: Notes | MIT | |
| UI UX Pro Maxsaoudi-h/solar-icons | 182 | 18 repos | ~11k | Automated safety check: Notes | Custom licence | |
| Creative Tim UI Blockscreativetimofficial/ui | 12k | — | ~2.1k | Automated safety check: Notes | MIT | |
| Cosscrafter-station/petdex | 4.2k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Convex Quickstart
spokvulcan/poker-planning
Creates or adds Convex to an app. An agent skill from spokvulcan/poker-planning.
UI UX Pro Max
saoudi-h/solar-icons
UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.
Creative Tim UI Blocks
creativetimofficial/ui
Helps install, generate and review Creative Tim UI blocks: shadcn/ui-based React and Tailwind sections that follow a restrained, production-minded design philosophy.
Coss
crafter-station/petdex
Helps implement coss UI components correctly. An agent skill from crafter-station/petdex.
Ss Learn
bitjaru/styleseed
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or…
Related
Categories
Questions about Game Changing Features
What does Game Changing Features do?
Find 10x product opportunities and high-leverage improvements. Game Changing Features is an agent skill from openstatusHQ/data-table-filters. Find 10x product opportunities and high-leverage improvements.
When should I use Game Changing Features?
Game Changing Features fits situations like: user wants strategic product thinking; wants to find high-impact features; says what would make this 10x better; product strategy.
How do I install Game Changing Features in Claude Code?
Run `npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a claude-code`. Or copy the skill folder (.agents/skills/game-changing-features in openstatusHQ/data-table-filters) into .claude/skills/game-changing-features in your project. Claude Code loads it when a task matches its description.
How do I install Game Changing Features in Codex?
Run `npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a codex`. Or copy the skill folder (.agents/skills/game-changing-features in openstatusHQ/data-table-filters) into .agents/skills/game-changing-features in your project. Codex loads it when a task matches its description.
Can I use Game Changing Features in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openstatusHQ/data-table-filters --skill game-changing-features -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/game-changing-features, .gemini/skills/game-changing-features, .github/skills/game-changing-features and .opencode/skills/game-changing-features in your project.
What does Game Changing Features need to run?
SKILL.md names no scripts, command-line tools or credentials: Game Changing Features is instructions for the agent only.
Does Game Changing Features access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Game Changing Features safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Game Changing Features use?
Game Changing Features is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Game Changing Features use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Game Changing Features?
Skills that share tags, products or a category with Game Changing Features: Buzzform (buildnbuzz/buzzform, 101 stars), Convex Quickstart (spokvulcan/poker-planning, 114 stars), UI UX Pro Max (saoudi-h/solar-icons, 182 stars) and Creative Tim UI Blocks (creativetimofficial/ui, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Game Changing Features?
openstatusHQ (a GitHub organization) maintains it in openstatusHQ/data-table-filters, which has 2,273 GitHub stars. The repository was last updated on October 2, 2026.
Source: openstatusHQ/data-table-filters on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.