Is apple-dev-research safe to install?

SaferSkills independently audited apple-dev-research (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/apple-dev-research/SKILL.md · 1 file

skills/apple-dev-research/SKILL.md2.3 KB · Markdown

name: apple-dev-research

description: Search Apple Dev Search for Swift, SwiftUI, Xcode, iOS, macOS, and Apple-platform community articles, tutorials, blogs, and write-ups.

Apple Developer Research

Bundled commands use $PLUGIN_ROOT ($env:PLUGIN_ROOT in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"), otherwise the absolute path of this plugin's root directory.

Use Apple Dev Search for Apple-platform community content when the user wants articles, tutorials, or reading material rather than official docs or generic web results. Do not hard-code service counts; query --counts when counts matter.

Workflow

Start with one focused query using the user's wording.
Hard cap ordinary requests at 3 commands total: initial search plus 2 retries. Stop once 3 useful candidates are found.
If broad/noisy, retry with --title-only and tighter terms.
Use syntax when helpful: quotes, |, -, *, ~1, parentheses.
For fresh reading lists, inspect --recent.
Verify selected article URLs with Crawl4AI only when snippets are insufficient or candidates are close. Avoid generic web search/Tavily/Firecrawl unless Crawl4AI fails.
Return 3-8 links with title, blog, date, URL, and one-line relevance.

Commands

python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --query 'build speed' --limit 5
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --query '"incremental builds" | "compile time"' --title-only --limit 5
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --query 'swift testing -uikit' --limit 5
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --recent --limit 8
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --counts

Use full text for errors/API/framework names; title-only for broad topics. Keep user terminology in at least one query before expanding synonyms.

Reusable search URL:

https://appledevsearch.com/#q=<urlencoded query>&titleOnly=true|false

Mention exact queries used, separate title-only vs full-text results, prefer direct article links, and say when results are weak or empty.

apple-dev-research— agent skill

Is apple-dev-research safe to install?

Apple Developer Research

Workflow

Commands

Audit the pieces. Scan the whole. Decide.