Skip to content
TrustedSkillsbeta
Back to all skills

Healthkit Code Review

Checked
existential-birds·vlatest·backend·Apache-2.0

Automates healthkit backend code reviews, identifying potential errors, inefficiencies, and adherence to best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add existential-birds/beagle --skill healthkit-code-review -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

existential-birds

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned existential-birds/beagle at d1a74899fb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d1a74899fb
Manifest
plugins/beagle-ios/skills/healthkit-code-review/SKILL.md
Scanned
5 files, 819 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The healthkit-code-review skill enables AI agents to analyze and critique code specifically for Apple HealthKit integration. It scans implementations for data privacy compliance, permission handling accuracy, and adherence to platform-specific guidelines.

When to use it

  • Before submitting code to App Store Review that involves accessing user health data.
  • When auditing existing integrations to ensure they request the minimal necessary permissions.
  • During development to verify that HKAuthorizationRequest flows are implemented correctly.
  • To check for common pitfalls in handling read-only versus write access scopes.

Key capabilities

  • Validates HealthKit permission requests against Apple's current guidelines.
  • Identifies potential privacy violations in data storage and transmission logic.
  • Reviews code structure for proper error handling during authorization failures.
  • Checks implementation of required background fetch configurations for health updates.

Example prompts

  • "Review this Swift file for HealthKit integration issues before I submit it to the App Store."
  • "Analyze these permission request blocks to ensure they follow Apple's privacy best practices."
  • "Check if my code correctly handles the transition from read-only to full write access in HealthKit."

Tips & gotchas

Ensure your project targets the latest iOS version, as HealthKit guidelines evolve frequently. This skill focuses on code logic; it cannot verify actual runtime behavior or network connectivity issues.