product-feature-availability

Investigate whether documented product features are actually available for specific regions, plans, and platforms.

10|2|Updated May 6, 2026
One-click install
npx skills add https://github.com/jcrabapple/hermes-skills --skill product-feature-availability-jcrabapple
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-feature-availability
Source: https://github.com/jcrabapple/hermes-skills/tree/main/product-feature-availability
Command: npx skills add https://github.com/jcrabapple/hermes-skills --skill product-feature-availability-jcrabapple

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product documentation and marketing pages often promise features that are not actually available in your region, account type, or plan tier. This Skill resolves that discrepancy by systematically cross-referencing official docs, user reports, marketing materials, and rollout announcements to determine real availability. ## Core Features & Use Cases - Multi-Source Verification: Cross-checks help center articles, Reddit and forum reports, support rep responses, and region-specific marketing pages. - Dependency Analysis: Verifies whether upstream features a capability relies on are actually available in the user's context. - Structured Synthesis: Produces a bottom-line verdict with evidence, likely root cause, verification steps, timeline, and workarounds. - Use Case: A user in the US cannot find a feature the help center describes. The Skill discovers the docs are templated from the UK version, the feature depends on an account type unavailable in the US, and provides manual workarounds. ## Quick Start Investigate whether the feature described in this support article is actually available for my account in my region.

Frequently Asked Questions about product-feature-availability

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

FAQPage Schema
How do I check if a product feature is available in my region?▼

Cross-reference the official help center article with user reports on Reddit and forums, then check region-specific marketing pages for redirects or geoblocking. Verify any dependent features are also available, since a missing upstream feature breaks the one you want.

Why does the documentation show a feature I cannot find in my app?▼

Docs are often templated across regions, so a US help center may describe UK-only features. Other causes include phased rollouts, plan tier restrictions, or features that were removed after the docs were written.

How to verify feature availability when docs and marketing disagree?▼

Prioritize patterns across multiple user reports and official support rep responses over marketing pages. Check timestamps on reports, watch for vague language like "rolling out" or "select markets", and test the feature paths directly in the app.

Does this work for checking banking or fintech feature availability?▼

Yes, it includes a reference on the US banking API landscape covering Plaid read-only limitations, Revolut API status, and Mercury Personal as the only US neobank with a personal API. This helps when investigating banking APIs or programmable money movement.

What are the limitations of investigating feature availability from public sources?▼

Single Reddit comments can be wrong, so conclusions require patterns across multiple reports. Features can be removed after being available, and companies may stay silent on timelines, so some investigations end with a "partially available" or unknown verdict.