How do I install the Platform Guide skill?

Run npx skillmds@latest add asunalabs/platform-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Platform Guide safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Platform Guide?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Platform Guide free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Platform Guide?

asunalabs (@asunalabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Platform Guide by asunalabs — Agent Skill

Name: Platform Guide
Author: asunalabs

Platform Guide

Answers how-to questions about third-party platforms (e.g. 'how to change theme in Shopify', 'set up a Stripe webhook', 'connect a domain in Vercel', Meta/TikTok/Google consoles, Laravel Forge, app stores) with fresh data: always WebSearch the current official guide first and cite it — never answer from stale memory. Use whenever the user asks how to do, configure, enable, or find anything in an external platform's UI, or to set up API credentials.

asunalabs Updated Sep 22, 2026

File contents

platform-guide — fresh-docs discipline for third-party platforms

Third-party dashboards change constantly (a real example: Forge's Oct-2025 UI rework renamed "aliases" to Custom Domains and made site-type choices one-shot — pre-rework instructions were confidently wrong). Stale memory produces walkthroughs that look right and waste an afternoon.

Rules

Search before instructing. Before any UI walkthrough, configuration guide, or credential-setup explanation for an external platform: WebSearch for the current official documentation (qualify the query with the current year where UIs churn). WebFetch the top official source. Cross-check a second source when steps are security-sensitive (OAuth scopes, webhooks, payment config).
Prefer official channels: platform docs > changelogs/release notes > reputable recent tutorials. If a dedicated plugin exists for the platform (e.g. a Shopify plugin), use its skills as the first stop — and never fabricate endpoints, GraphQL fields, or doc URLs.
Cite freshness: note the source and fetched date (platform docs <url> (fetched YYYY-MM-DD)), consistent with the docs convention. If the live UI may differ from the doc, say so and offer to verify against the real dashboard (browser MCP) instead of guessing.
API versions matter: pin/mention the API version rather than "latest", and check deprecation notices for anything the instruction depends on.
If search is unavailable, say the answer is from memory as of the knowledge cutoff and mark every step that could have changed — don't present stale steps as current.

---name: platform-guidedescription: Answers how-to questions about third-party platforms (e.g. 'how to change theme in Shopify', 'set up a Stripe webhook', 'connect a domain in Vercel', Meta/TikTok/Google consoles, Laravel Forge, app stores) with fresh data: always WebSearch the current official guide first and cite it — never answer from stale memory. Use whenever the user asks how to do, configure, enable, or find anything in an external platform's UI, or to set up API credentials.---# platform-guide — fresh-docs discipline for third-party platformsThird-party dashboards change constantly (a real example: Forge's Oct-2025 UIrework renamed "aliases" to Custom Domains and made site-type choices one-shot —pre-rework instructions were confidently wrong). Stale memory produces walkthroughsthat look right and waste an afternoon.## Rules1. **Search before instructing.** Before any UI walkthrough, configuration guide, or credential-setup explanation for an external platform: WebSearch for the current official documentation (qualify the query with the current year where UIs churn). WebFetch the top official source. Cross-check a second source when steps are security-sensitive (OAuth scopes, webhooks, payment config).2. **Prefer official channels**: platform docs > changelogs/release notes > reputable recent tutorials. If a dedicated plugin exists for the platform (e.g. a Shopify plugin), use its skills as the first stop — and **never fabricate endpoints, GraphQL fields, or doc URLs**.3. **Cite freshness**: note the source and fetched date (`platform docs <url> (fetched YYYY-MM-DD)`), consistent with the docs convention. If the live UI may differ from the doc, say so and offer to verify against the real dashboard (browser MCP) instead of guessing.4. **API versions matter**: pin/mention the API version rather than "latest", and check deprecation notices for anything the instruction depends on.5. If search is unavailable, say the answer is from memory as of the knowledge cutoff and mark every step that could have changed — don't present stale steps as current.

Frequently asked questions