GitHub
Skills harvested from GitHub repositories
14810 skills availableapple-notes-observability
Apple Notes has no built-in metrics API or health endpoint. Observability must be built from the outside: polling note c...
apple-notes-migration-deep-dive
Migrating to or from Apple Notes requires understanding that Notes stores content as proprietary HTML with no REST API f...
apple-notes-hello-world
Create, read, search, and delete Apple Notes using JXA (JavaScript for Automation) via osascript. All examples work from...
apple-notes-incident-runbook
This runbook covers the most common Apple Notes automation failures and their resolution procedures. Unlike cloud SaaS i...
apple-notes-deploy-integration
Apple Notes automation runs exclusively on macOS — there is no cloud deployment path because Notes.app depends on the lo...
apple-notes-enterprise-rbac
Apple Notes has no built-in role-based access control (RBAC). In enterprise environments with Managed Apple IDs via Appl...
apple-notes-data-handling
Apple Notes stores note content as a restricted subset of HTML internally. The body() property in JXA returns this HTML,...
apple-notes-cost-tuning
Apple Notes itself is free with every Apple ID. The only real cost is iCloud storage, which is shared across Photos, iCl...
apple-notes-core-workflow-a
Primary workflow: automate Apple Notes management with batch creation, template-based note generation, folder organizati...
apple-notes-core-workflow-b
Export Apple Notes to portable formats: Markdown, JSON, HTML files, and SQLite databases. Apple Notes stores content as ...
apify-webhooks-events
Configure webhooks to receive notifications when Actor runs complete, fail, or time out. Apify supports both persistent ...
apple-notes-common-errors
Apple Notes automation errors fall into three categories: TCC permission denials from macOS security, AppleEvent communi...
apify-upgrade-migration
Guide for upgrading apify, apify-client, and crawlee packages. The biggest migration in Apify's history was SDK v2 to v3...
apify-local-dev-loop
Build and test Apify Actors on your local machine before deploying to the platform. Uses the Apify CLI (apify run) which...
apify-reference-architecture
Production-ready architecture patterns for applications built on Apify. Covers standalone Actor projects, multi-Actor pi...
apify-install-auth
Set up the Apify ecosystem: the apify-client JS library (for calling Actors remotely), the apify SDK (for building Actor...
apify-core-workflow-b
Manage Apify's three storage types (datasets, key-value stores, request queues) and orchestrate multi-Actor pipelines. C...
apify-cost-tuning
Apify charges based on compute units (CU), proxy traffic (GB), and storage. One CU = 1 GB memory running for 1 hour. Thi...
anima-upgrade-migration
| From | To | Complexity | |------|----|-----------| | Figma plugin (manual) | SDK automation | Medium | | SDK v1 → v2 |...
anima-security-basics
[ ] Anima token stored in secret manager (not .env in prod) [ ] Figma PAT has minimum required scope (file:read only) [ ...
anima-performance-tuning
| Operation | Target | Notes | |-----------|--------|-------| | Single component generation | < 10s | Depends on complex...
anima-sdk-patterns
Production patterns for @animaapp/anima-sdk: singleton client, generation caching, output normalization, and configurabl...
anima-hello-world
Generate production-ready React, Vue, or HTML code from a Figma design using the @animaapp/anima-sdk. This example conve...
anima-local-dev-loop
Iterative development workflow for Anima design-to-code: generate from Figma, preview in browser, tweak settings, regene...