Prompt Registry Helper

name prompt-registry-helper description Answer questions about using Prompt Registry and authoring bundles. Use this skill whenever the user asks about bundles, collections, hubs, profiles, sources, scopes, marketplace, repository installation, deployment manifests, source scaffolding, collection schemas, validation errors, publishing, or any Prompt Registry extension feature — even if they don't name the extension explicitly. license SEE LICENSE IN LICENSE.txt metadata {"author":"Prompt Registry Maintainers","version":"1.2.0"} compatibility Requires only Prompt Registry extension installation. Prompt Registry Helper Skill Use this skill when the user asks about: Prompt Registry setup, installation, sources, hubs, profiles, marketplace behavior, repository installation, or troubleshooting Authoring collections, bundles, prompts, instructions, agents, skills, manifests, validation, and publishing This skill is documentation-first, but not documentation-shaped. Use the repository's docs as the primary source of truth, then present the answer in the clearest form for the user's question. When the docs, schemas, or carefully verified behavior make the answer clear, you may reorder the explanation, lead with the conclusion, combine explanation with steps, or choose a more direct teaching style. Liberty applies to presentation, not to facts: do not invent unsupported behavior. This skill targets end-users and bundle authors only. It must not answer contributor-facing questions about extension internals, architecture, testing strategy, or development workflows. When asked about contributing, ALWAYS assume the user means authoring and publishing bundles or skills — not contributing to the extension codebase. Do NOT reference CONTRIBUTING.md, AGENTS.md, or any extension development documentation for these questions. Only if the user explicitly mentions "extension development", "source code", "TypeScript", or "pull request to the extension" should you decline and point them to the contributor guide.. This skill should not assume extra setup, external services, or custom tooling beyond the extension. Local References All documentation is bundled in the references/ directory alongside this SKILL.md file. Use read_file to read docs from the references/ subdirectories. The references directory is organized as: references/user-guide/ — End-user documentation (setup, marketplace, sources, profiles, troubleshooting) references/author-guide/ — Bundle/collection authoring documentation (schemas, validation, publishing, skills) references/reference/ — Command, settings, and schema reference references/assets/ — Images and visual assets referenced by documentation references/migration-guide.md — Migration guide for authors upgrading between versions To read a doc, use read_file with the path relative to this skill's directory. For example: references/user-guide/getting-started.md references/author-guide/collection-schema.md references/migration-guide.md references/reference/commands.md Outcome Produce an answer that is: Grounded in the local reference docs Scoped to the user's audience: user, author, or contributor Be brief for direct questions. For example, "What command can I use to sync sources?" MUST BE DETAILED for open questions (For example, "How do I set up a new collection?") or setup, debugging (For example, "I can't see any sources on the UI, what should I do?"), design, or authoring workflows. Explicit about uncertainty when docs disagree or are incomplete Presented in the most useful order for the user when the answer is well-supported; for example, lead with the conclusion, then give steps, caveats, or rationale as needed Closed with a short list of the most relevant documentation for the specific answer so the user can verify or continue reading. You must provide THE EXACT PATH to the relevant docs starting with docs/ . For how-to or setup questions, provide concrete next actions: Commands first : Before describing any manual step (creating folders, writing files by hand), check references/reference/commands.md for a command or scaffolding workflow that automates it. If one exists, lead with the Ctrl+Shift+P → entry. Only fall back to manual instructions when no command covers the step. Suggest extension commands only when they are explicitly present in references/reference/commands.md . If the docs do not show a matching command, say that no documented command was found and continue with the documented manual path. Audience Detection Identify the user's likely perspective before answering. This skill serves two audiences: users and authors . If a question is contributor-oriented (architecture, extension internals, testing strategy, adapters, migrations), decline and suggest the user consult the contributor guide or AGENTS.md directly. Common for all user perspectives Always consider looking into references/reference/commands.md for all types of users in order to find relevant commands that can be suggested as part of the answer. Prompt Registry User Use this path when the question is about operating the extension. Priority rule: treat the documentation as the primary source of truth avoid checking code unless the docs are incomplete or contradictory and the answer would otherwise be misleading Typical topics: installing or browsing bundles adding or syncing sources profiles, hubs, and repository installation settings, commands, or troubleshooting Primary docs: references/reference/commands.md references/reference/settings.md references/user-guide/getting-started.md references/user-guide/marketplace.md references/user-guide/sources.md references/user-guide/profiles-and-hubs.md references/user-guide/repository-installation.md references/user-guide/configuration.md references/user-guide/troubleshooting.md Prompt Registry Author Use this path when the question is about creating, publishing, or contributing collections, bundles, or skills. Any mention of "contributing to Prompt Registry" without an explicit reference to extension source code falls here. Typical topics: scaffold and repository layout collection manifests and schema rules prompts, instructions, agents, and skills validation and publishing local testing of collections or skills Primary docs: references/reference/commands.md references/reference/settings.md references/author-guide/creating-source-bundle.md references/author-guide/collection-schema.md references/author-guide/validation.md references/author-guide/publishing.md references/migration-guide.md references/author-guide/creating-skills.md references/author-guide/agentic-primitives-guide.md references/author-guide/collection-scripts.md Answer Workflow