Apple dash docsets
Provide essential skills for Apple development, including Xcode workflows, Dash docset management, and Swift package scaffolding and verification.
npx -y skills add Syniox5334/apple-dev-skills --skill apple-dash-docsetsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Manage Dash docsets and cheatsheets on macOS. Use when tasks involve Dash search and discovery, installing missing docsets, or generating guidance when a docset is unavailable.
SKILL.md
5.3 KB, as published. Nobody here has run it
Apple Dash Docsets
Purpose
Manage Dash docsets and cheatsheets on macOS with one top-level entry point. scripts/run_workflow.py is the authoritative runtime path for stage selection, fallback order, source priority, approval gating, and structured generation guidance; it does not replace the agent's own Dash access methods.
When To Use
- Use this skill for Dash search and discovery requests.
- Use this skill for Dash installation requests after search has identified a missing docset.
- Use this skill for Dash generation guidance when installation cannot complete.
- Use this skill when the user needs the exact fallback path between agent-side Dash MCP usage, local HTTP, and URL or Service integration.
- Recommend
apple-xcode-workflowwhen the user needs Apple or Swift execution, diagnostics, build or test work, or Apple docs reasoning outside Dash management. - Recommend
apple-swift-package-bootstrapwhen the user is starting a brand new Swift package rather than managing Dash content.
Single-Path Workflow
- Classify the request into one stage:
searchinstallgenerate
- If no stage is explicit, start at
search. - Run
scripts/run_workflow.pywith the selected stage:search: applies configured fallback order and returns a structured access-path decisioninstall: applies configured source priority and approval gatinggenerate: returns structured automation-first guidance
- If the selected stage cannot complete, hand off forward through
references/stage-handoff-contract.md:search -> installinstall -> generate
- Return one status, one
path_type, and one output contract for the stage that ran.
Inputs
stage:search,install, orgeneratequery: required forsearchdocset_identifiers: optional forsearch; use installed identifiers onlydocset_request: required forinstallandgenerateapproval: required before side-effectful install actions- Defaults:
- runtime entrypoint:
python3 scripts/run_workflow.py searchaccess order ismcp -> http -> url-service- install source priority is
built-in,user-contributed,cheatsheet - default search result limit is
20 - default search snippets setting is
true
- runtime entrypoint:
Outputs
statussuccess: the selected stage completed on its primary or fallback pathblocked: prerequisites, approval, or usable access paths are missinghandoff: the current stage is handing off to the next Dash stage
path_typeprimary: the selected stage completed normallyfallback: the selected stage completed through its documented fallback path
outputstageaccess_pathorsource_pathmatches- install result or generation guidance when applicable
- one next step when follow-up is required
Guards and Stop Conditions
- Do not run install actions without explicit user approval.
- Do not invent docset identifiers or catalog matches.
- Stop with
blockedwhen agent-side Dash MCP usage, HTTP, and URL or Service paths are all unusable forsearch. - Stop with
blockedwheninstallorgeneratelacks a concrete docset request. - Keep
search,install, andgeneratein forward stage order; do not blend them into competing primary workflows.
Fallbacks and Handoffs
searchfalls back in this order: agent-side Dash MCP usage, local HTTP API, then URL or Service guidance.installhands off togeneratewhen no installable catalog match exists.generatefalls back from stable automation to deterministic manual guidance.- Use
references/stage-handoff-contract.mdwhensearchtransitions toinstallorinstalltransitions togenerate. - Recommend
apple-xcode-workflowdirectly when the user’s task shifts from docs management to Apple or Swift execution work. - Recommend
apple-swift-package-bootstrapdirectly when the user needs new Swift package scaffolding. scripts/run_workflow.pyis the only local runtime entrypoint for stage behavior; helper scripts remain implementation details behind it.
Customization
- Use
references/customization-flow.md. scripts/customization_config.pystores and reports customization state.scripts/run_workflow.pyloads and enforces the runtime-safe knobs documented inreferences/customization-flow.md.
References
Workflow References
references/dash_mcp_tools.mdreferences/dash_http_api.mdreferences/dash_url_and_service.md
Contract References
references/stage-handoff-contract.mdreferences/automation-prompts.mdreferences/customization-flow.md
Support References
- Recommend
references/snippets/apple-swift-core.mdwhen the user needs a reusable Apple and Swift baseline snippet in their own repo alongside Dash-based docs workflows. references/catalog_built_in_docsets.jsonreferences/catalog_user_contrib_docsets.jsonreferences/catalog_cheatsheets.jsonreferences/snippets/apple-swift-core.md
Script Inventory
scripts/run_workflow.pyscripts/dash_api_probe.pyscripts/dash_catalog_match.pyscripts/dash_catalog_refresh.pyscripts/dash_url_search.pyscripts/dash_url_install.py