shopify-connections
Skill2 starsChanged 39 days agoMITView on GitHub
Guide safe Shopify Dev Dashboard, Partner Dashboard and CLI account setup, plus optional Apify CLI research access, without requiring MCP or collecting credentials.
In this repository35 other files it gives its agents.
- admin-graphqlSkill
- admin-restSkill
- app-accessibilitySkill
- app-authSkill
- app-billingSkill
- app-bridgeSkill
- app-frameworkSkill
- app-listing-optimizationSkill
- app-market-researchSkill
- app-namingSkill
- app-niche-finderSkill
- app-performanceSkill
- app-pricing-strategySkill
- app-release-readinessSkill
- app-validationSkill
- b2b-marketsSkill
- built-for-shopify-standardsSkill
- dev-troubleshootingSkill
- hydrogen-storefrontSkill
- liquid-themesSkill
- merchant-pain-preventionSkill
- metafields-metaobjectsSkill
- polaris-uiSkill
- shopify-app-store-adsSkill
- shopify-cliSkill
- shopify-functionsSkill
- shopify-project-copilotSkill
- storefront-apiSkill
- top-app-ux-patternsSkill
- using-shopify-app-builderSkill
- ux-empty-error-statesSkill
- ux-modern-app-feelSkill
- ux-onboardingSkill
- ux-polaris-antipatternsSkill
- webhooksSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Run shopify app dev against the approved dev store, complete the install approval, then verify an embedded page and an authenticated read.
- Distinctive: line 26
Use the Partner Dashboard only when needed for partner/business or distribution steps.
- Distinctive: line 37
If access is denied, name the missing app developer role and provide the official permission guide.
- Distinctive: line 38
Do not request access to other organizations, production stores, or unrelated Actors.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Connect only what you need
A connection here means an official browser sign-in or CLI session owned by the user—not a bundled remote server or invented connector ID.
Choose the minimum setup
| Purpose | Connection | Needed now? |
| Plan, review code, use examples | None | Works offline with files |
| Scaffold/test an app | Shopify CLI + Dev Dashboard org/app/dev store | When testing live |
| Partner business, distribution and payouts | Partner Dashboard | Only for that workflow |
| Competitor/review research | Apify CLI or a Console export | Optional |
Shopify setup, one step at a time
- Inspect non-secret versions with shopify version and installed help. If absent, explain the official CLI installation prerequisites and proposed install before acting.
- Open the official Dev Dashboard. The user chooses the correct organization and an authorized dev store; app developer access may require the organization owner.
- For a new project use the current shopify app init flow; for an existing one inspect shopify app info. Let Shopify's supported command open browser sign-in when needed. Don't invent a separate auth command or extract a cached session.
- Explain app config link can create/overwrite local configuration; confirm the selected app and preserve existing config before linking.
- Run shopify app dev against the approved dev store, complete the install approval, then verify an embedded page and an authenticated read. Record only non-secret organization/app/store identifiers in the user's project notes.
- Use the Partner Dashboard only when needed for partner/business or distribution steps. App creation/configuration has moved to Dev Dashboard. Verify the current dashboard path rather than following old screenshots.
Optional Apify connection
Explain an Actor is a hosted program that can incur charges. Use the official Apify CLI or let the user export public results from Console. The user completes apify login themselves through the official supported flow. Never use a token-display command, inspect the CLI credential file, or pass a token in an argument or URL. Inspect apify --version and apify actors info khadinakbar/shopify-app-store-scraper --input, then use app-market-research. No paid call is authorized by login or input inspection.
Verify / recover
Connected is not the same as installed or tested. Confirm the intended org/app/dev store via supported non-secret status, and the working app in the dev store. If access is denied, name the missing app developer role and provide the official permission guide. If no CLI/browser is available, give a checklist or manual Console path and continue offline work. Do not request access to other organizations, production stores, or unrelated Actors.
Sources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.