Skip to content
TrustedSkillsbeta
Back to all skills

Safe Area Handling

Checked
cap-go·vlatest·frontend·MIT

This skill safely manages and handles designated areas within a simulation, preventing unintended interactions and ensuring controlled environments.

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 cap-go/capgo-skills --skill safe-area-handling -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

cap-go

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 cap-go/capgo-skills at bc99163045.

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

Scanned
8 files, 544 lines
Copies in repo
2 — all of them scanned
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

What it does

This skill, Safe Area Handling, enables AI agents to manage and correctly display content on devices with notches (iPhones), Dynamic Islands, home indicators, Android cutouts, or other screen obstructions. It provides CSS solutions for ensuring that content isn't hidden by these elements and allows for fullscreen layouts that respect the device’s safe areas. The skill utilizes viewport coverage and CSS environment variables to adjust padding and positioning dynamically.

When to use it

  • When experiencing layout issues on devices with notches or cutouts.
  • When a user specifically asks about safe area considerations.
  • If content is being obscured by the home indicator or notch.
  • To achieve a fullscreen application layout that accounts for device-specific screen features.
  • When needing to ensure all elements are visible and properly positioned on various devices.

Key capabilities

  • Handles iPhone notches, Dynamic Islands, and home indicators.
  • Manages Android cutouts and navigation gestures.
  • Provides CSS solutions using environment variables (e.g., safe-area-inset-top, safe-area-inset-bottom).
  • Enables viewport coverage via the <meta> tag (viewport-fit=cover).
  • Supports full page layouts that respect safe area insets.

Example prompts

  • "How can I prevent my header from being hidden by the iPhone notch?"
  • "What's the best way to ensure content is visible on Android devices with cutouts?"
  • "I need a fullscreen layout that respects the device’s safe areas; how do I achieve this?"

Tips & gotchas

  • The viewport-fit=cover attribute in the <meta> tag is required for accessing safe area insets. Without it, padding calculations will not work correctly.
  • This skill focuses on CSS solutions and does not address underlying layout design issues; it provides adjustments to existing layouts.