nexscope-ai/nexscope-ecommerce-skills / ecommerce-amazon-category-lookup
ecommerce.amazon-category-lookup
VerifiedBrowse Amazon category nodes by parent identifier or search category metadata by name. Use this skill when the user asks for this exact ecommerce workflow, analysis, data lookup, or deliverable.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| manifest.json | config | 618 B |
| references/api.json | config | 1.1 KB |
| references/api.md | markdown | 3.6 KB |
| references/credentials.md | markdown | 984 B |
| references/testing.md | markdown | 1.0 KB |
| references/workflow.md | markdown | 1.2 KB |
| scripts/amazon_category_lookup.py | script | 11.2 KB |
references/credentials.md
View on GitHub# Runtime Configuration and Credentials
Set only the variables required by the selected package-local script. Keep secrets in the environment; never place credentials in CLI arguments, saved payloads, logs, or generated reports.
| Variable | Classification |
|---|---|
| `APP_NAME` | runtime configuration |
| `MESSAGE_ID` | runtime configuration |
| `MODE_ID` | runtime configuration |
| `NEXSCOPE_API_KEY` | secret credential |
| `NEXSCOPE_PROXY_BASE` | runtime configuration |
| `NEXSCOPE_WORKSPACES` | runtime configuration |
| `SESSION_ID` | runtime configuration |
Business and tool-service clients use `NEXSCOPE_PROXY_BASE` with `NEXSCOPE_API_KEY`. Because authorization/account routes are not implemented in that proxy, account workflows use the relevant independently configured `NEXSCOPE_AGENT_*` or `NEXSCOPE_LOGIN_*` base. Third-party connectors use their named provider credentials and endpoints. Missing configuration must fail closed without printing secret values.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |