List accessible XBTI personality test cases from verified community addresses or repositories.
Triggers
Activate when
- "List accessible XBTI personality test cases from verified community addresses or repositories."
- “Browse a gallery of XBTI personality tests.”
Do not activate when
- Only querying this Skill's description, or requesting tasks unrelated to the above results; no actual business operations are performed.
- When the user only wants to preview or review, do not enter the modify, commit, or publish branches.
Execution boundary
A natural language request is sufficient to trigger it; no legacy slash path, parameter interpolation, or specified assistant is needed. Explicitly parse the project, target files, options, and output location in the current request; use the file, search, CLI, and browser capabilities actually provided by the current host. Project dependency versions and external APIs are verified at execution time; do not assume the examples are current configurations. Package scripts are resolved from the Skill root, business files are resolved from the target project root. Read the current state first, and protect existing uncommitted content and the staging area of other tasks. Analysis and preview requests remain read-only; modification, commit, push, deployment, and publication each execute according to the explicit scope of the current request. Do not bypass protections, automatically send messages, forcibly terminate user processes, or seize the foreground. On failure, retain the diagnosable original error.
Workflow
-
Obtain the gallery URL or repository from the user request, project configuration, or Profile; do not treat legacy example domains as the real official website.
-
First verify the address and access status. When the user asks to open the page, use the available browser entry point; when only a list is requested, remain read-only retrieval.
-
In repository mode, read names and descriptions through the cases directory of the confirmed repo, handle pagination and path encoding, and preserve the real URLs.
-
Empty directories, 404s, insufficient permissions, and parsing failures are explained separately; when inaccessible, do not falsely report that there are no cases.
-
The results state the test names, brief descriptions, and available entry points; do not create tests, do not commit cases, and do not use personality test results for clinical judgment.
Composition
Before execution, read capability combination, and hand off to adjacent capabilities according to the explicit artifact.
Runtime context (shared)
Before running, read this package's skill.yaml and Profile contract. Priority is the current request,
project context, this Skill's records, shared preferences, brand/user Profile, security defaults.
Only read declared fields; hosts without a dedicated runtime may use scripts/profile_store.py to read the shared Profile.
For missing configuration, ask only one question that affects the result. Values the user explicitly requests to save long-term are atomically written through that script,
report the actual path; do not save inferences, credentials, or materials from other tasks.