screen-time-api-engineer
npx machina-cli add skill Siddhu7007/screen-time-api-agent-skill/screen-time-api-engineer --openclawScreen Time API Engineer
Use this skill to implement and harden Screen Time API apps with a docs-first evidence model.
Rules
- Use this evidence order for decisions:
- Canonical Apple docs and WWDC
- Local SDK interfaces/headers
- Project-observed implementations (Project Alpha/Project Beta)
- Field notes (forums/medium)
- If sources conflict, prefer canonical + SDK behavior.
- Mark uncertain conclusions as inference and include a caveat.
Quick Start Workflow
- Identify user goal category.
- Open matching references from
references/guides. - Cross-check critical API claims in
references/evidence. - If implementation quality or regressions matter, use
references/rundowns. - Produce output with explicit source/confidence labeling.
Goal to Reference Map
- Entitlements, signing, distribution approval:
references/guides/02-authorization-setup.mdreferences/guides/19-release-and-app-review-checklist.md
- Family activity picker and token handling:
references/guides/03-familycontrols-selection-and-token-model.mdreferences/guides/04-displaying-activity-labels-and-real-app-icons.md
- Shield policy and store behavior:
references/guides/05-managedsettings-enforcement-patterns.mdreferences/guides/06-web-blocking-and-webdomain-policy.md
- Custom shield UI/action:
references/guides/07-managedsettingsui-custom-shield-systems.mdreferences/guides/08-shield-actions-and-response-strategies.md
- Scheduling and monitor callbacks:
references/guides/09-deviceactivity-scheduling-thresholds-and-errors.mdreferences/guides/10-deviceactivity-monitor-extension-playbook.md
- Usage analytics reporting:
references/guides/11-deviceactivity-report-analytics-architecture.md
- Web usage control/reporting via ScreenTime framework:
references/guides/12-screentime-framework-web-usage-reporting.md
- Onboarding and permission UX:
references/guides/13-onboarding-and-permission-ui-blueprints.md
- End-to-end implementation reference:
references/guides/14-app-and-website-blocking-reference-implementation.md
- Project deep dives and comparative hardening:
references/guides/15-project-alpha-implementation-analysis.mdreferences/guides/16-project-beta-implementation-analysis.mdreferences/rundowns/12-cross-project-rundown.md
- Bug prevention, testing, and preflight:
references/guides/17-hardening-checklist-bug-prevention.mdreferences/guides/18-testing-matrix-device-only-edge-cases.mdreferences/guides/21-preflight-rundown.md
Evidence Files (Use When Verifying API Contracts)
references/evidence/01-familycontrols-sdk-signatures.mdreferences/evidence/02-managedsettings-sdk-signatures.mdreferences/evidence/03-managedsettingsui-sdk-signatures.mdreferences/evidence/04-deviceactivity-sdk-signatures.mdreferences/evidence/05-deviceactivity-report-sdk-signatures.mdreferences/evidence/06-screentime-framework-headers.mdreferences/evidence/07-claim-reconciliation.mdreferences/evidence/00-source-url-inventory.md
Output Contract
When using this skill for implementation guidance, include:
- Chosen API path and why.
- Risks/failure modes.
- Validation checklist.
- Source citations with confidence labels.
Boundaries
- Do not infer private APIs or unsupported token conversion techniques.
- Do not claim behavior beyond canonical/SDK support without explicit caveats.
- Do not skip extension-signing parity checks when discussing release readiness.
Source
git clone https://github.com/Siddhu7007/screen-time-api-agent-skill/blob/main/skills/screen-time-api-engineer/SKILL.mdView on GitHub Overview
Helps you implement and harden Screen Time API apps using FamilyControls, ManagedSettings, ManagedSettingsUI, ScreenTime, and DeviceActivity extensions. Covers app/website blocking, custom shields, shield actions, scheduling, onboarding flows, analytics, entitlements, App Review readiness, debugging, and production hardening.
How This Skill Works
Uses a docs-first evidence model: start with canonical Apple docs and WWDC, then verify against local SDK headers, compare with project implementations, and corroborate with field notes. Output includes explicit source citations and confidence labeling to guide implementation and risk assessment.
When to Use It
- Build app and website blocking workflows using FamilyControls and store-enforced policies.
- Design custom shields and shield action handling through ManagedSettingsUI.
- Implement schedule-based enforcement and DeviceActivity monitoring callbacks.
- Prepare onboarding flows and entitlements for App Store submission and approvals.
- Develop usage analytics reporting and preflight hardening for production readiness.
Quick Start
- Step 1: Identify user goal category
- Step 2: Open matching references from references/guides
- Step 3: Cross-check critical API claims in references/evidence and produce output with explicit source labeling
Best Practices
- Anchor decisions to canonical Apple docs and WWDC content before SDK claims.
- Cross-check API claims against SDK headers and public interfaces.
- Document sources and assign clear confidence levels for each conclusion.
- Avoid private APIs and unsupported token conversion techniques.
- Perform thorough preflight, hardening checks, and regression testing before release.
Example Use Cases
- Block a social app after school hours according to a family policy using Schedule + Shield.
- Deploy a custom shield UI that blocks specific websites with a user override option.
- Handle shield actions with a defined response strategy to re-evaluate after a timeout.
- Run an onboarding flow to obtain user consent and required entitlements for Screen Time.
- Generate usage analytics reports via DeviceActivity and validate them in preflight checks for App Review.