Index of every page on this site: llms.txt
All skills
rshankras avatar

/privacy-publish

@f958982
Run it yourself

Turn drafted legal docs (privacy policy, terms) into hosted pages and set the App Store Connect Privacy Policy / Support / Marketing URLs via the ASC REST API. Use at Phase 6 / submission, after legal drafts exist. The App Privacy "nutrition label" stays manual (Apple exposes no API) — this prints the exact answers to click.

Use this Skill: https://skilld.dev/gh/rshankras/claude-code-apple-skills/privacy-publish

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈86 tokens for metadata: the name and description. ≈836 when used: this file.

Description uses 4.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈344 characters, or 4.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Privacy Publish

Close the "hosted legal pages + ASC URLs" gap: render .planning/legal/{privacy,terms}.md → host them → PATCH the Privacy/Support URLs onto the App Store version. The one thing with no API — the App Privacy nutrition label — is handed off as a precise checklist.

Depends on the user's web infra, so ask once, remember. Hosting choice is theirs; the ASC URL-setting is the automatable part.

Prerequisites

  • Legal drafts exist: .planning/legal/privacy.md, .planning/legal/terms.md (from legal/privacy-policy).
  • _shared/asc-api/ set up (README).
  • Set ASC="python3 <path to asc.py>" — resolve asc.py relative to this SKILL.md file's location (../../_shared/asc-api/asc.py), never the project cwd. Known install locations:
    • SwiftShip symlink install: ~/.claude/swiftship-skills/_shared/asc-api/asc.py
    • Copied install: .claude/skills/_shared/asc-api/asc.py (project) or ~/.claude/skills/_shared/asc-api/asc.py (global)
    • Plugin install: resolve from this file's location — the _shared/ tree ships with the plugin.
    • npx skills install: the installer copies only this skill's folder, so _shared/ is missing. Clone https://github.com/rshankras/claude-code-apple-skills and use <clone>/skills/_shared/asc-api/asc.py.
  • The app has a current editable App Store version + an en-US appInfoLocalization and appStoreVersionLocalization (get their ids first).

Flow — dry-run → confirm → apply

  1. Render. Markdown → minimal self-contained HTML (or keep .md if the host renders it).
  2. Publish (pick per the user's infra — AskUserQuestion once, then remember in .planning/):
    • git static site — commit + push to the pages repo/branch.
    • WordPress — POST /wp-json/wp/v2/pages with an application password.
    • Netlify / S3 / other — the host's CLI.
    • Browser fallback — drive the CMS with claude-in-chrome (detect → preview → confirm → act → fall back, per TOOL-HANDOFF.md).
    • Confirm both URLs resolve (HTTP 200) before touching ASC.
  3. Set the ASC URLs (REST — dry-run, confirm, then --apply):
    • Privacy Policy URL → appInfoLocalizations (privacyPolicyUrl):
      $ASC PATCH /v1/appInfoLocalizations/<id> '{"data":{"type":"appInfoLocalizations","id":"<id>","attributes":{"privacyPolicyUrl":"https://…/privacy"}}}' --apply
    • Support / Marketing URL → appStoreVersionLocalizations (supportUrl, marketingUrl) — PATCH the current version's en-US localization id.
  4. Nutrition label (manual — no API). Emit a checklist matching Sources/PrivacyInfo.xcprivacy (e.g. Data Not Collected, no tracking) for the user to click in ASC ▸ App Privacy. Do not claim this step is automated.

Done

  • Legal pages live + resolving; Privacy/Support URLs set via API; nutrition-label checklist handed off.

Caveats

  • Verify each endpoint/field against the current ASC API reference before --apply (captured 2026-07).
  • Confirm URLs return 200 before setting them in ASC — a dead Privacy URL is a common rejection (Guideline 5.1.1).
  • The nutrition label and some age-rating specifics have no public API — those remain ASC-UI/manual by design.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts10d3 checks · Risk SAFE
  • Gen Agent Trust Hub10d

    The skill automates the deployment of legal documents and updates App Store Connect metadata using a custom Python script. It presents surfaces for command injection and indirect prompt injection through project files.

  • Socket11d

    No alerts

  • Snyk10d

    Risk: LOW · No issues

Signed by skilld at f958982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago
What it can do
Reads files Runs commands
MCP servers
claude-in-chrome
last_verified
2026-11-09
review_by
2027-06-22
All 6 allowed tools
ReadBashAskUserQuestionmcp__claude-in-chrome__navigatemcp__claude-in-chrome__computermcp__claude-in-chrome__read_page

README badge

README badge for rshankras/claude-code-apple-skills/privacy-publish