CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

browserenginekit

Build alternative browser engines using BrowserEngineKit. Use when developing a non-WebKit browser engine for iOS/iPadOS in supported regions, managing web content/rendering/networking extension processes, configuring GPU and networking process capabilities, checking alternative-engine device eligibility, or reviewing BrowserEngineKit entitlements and Info.plist setup.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is dpearson2699/swift-ios-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, framework-dense reference: executable Swift examples, entitlement tables, WRONG/CORRECT mistake patterns, and a thorough review checklist, with details correctly offloaded to a single well-organized reference file. Weaknesses are mild: some entitlement/architecture guidance is repeated across sections, the JIT snippet is placeholder-style, and workflows lack explicit validation-feedback loops.

Suggestions

Consolidate the JIT entitlement requirements (currently in both 'Entitlements' and 'Sandbox and Security') and the arm64e guidance (currently in 'Sandbox and Security' plus the checklist) into single sections cross-referenced once, trimming the duplicated prose.

Replace the ellipsis placeholders in the JIT example ('be_memory_inline_jit_restrict_rwx_to_rw_with_witness(...)') with a complete call, and briefly define or link the 'networkProxy'/'renderProxy'/'contentProxy' pattern used in the bootstrap Common Mistake example (it lives only in the references file).

Add explicit validation checkpoints to key workflows — e.g., after applyRestrictedSandbox and after signing the archive, state what to verify and how to recover if the check fails — to upgrade the checklist from end-state audit to in-flight feedback loop.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, framework-specific facts and uses token-efficient tables for entitlements and capabilities. However, JIT entitlement requirements are stated in both the 'Entitlements' and 'Sandbox and Security' sections, arm64e guidance appears in both 'Sandbox and Security' and the checklist, and the 'DON'T: Hard-code region eligibility' mistake restates the eligibility section — minor over-explanation that could be tightened. Not 3 because there is no padding explaining concepts Claude already knows; not 5 because of the duplicated entitlement/architecture guidance.

4 / 5

Actionability

Mostly executable guidance: complete Swift snippets for WebContentProcess/NetworkingProcess/RenderingProcess launch, makeLibXPCConnection, grantCapability, MediaEnvironment, applyRestrictedSandbox, and BEAvailability eligibility. Minor gaps keep it below 5: the JIT snippet uses ellipsis placeholders ('be_memory_inline_jit_restrict_rwx_to_rw_with_witness(...)') rather than a complete call, and the Common Mistakes bootstrap example references 'networkProxy'/'renderProxy' objects never introduced in the body. Not 3 because the code is real and largely copy-paste ready, not pseudocode.

4 / 5

Workflow Clarity

The bootstrap sequence is a clear numbered 1-5 list, architecture is diagrammed, Common Mistakes give explicit WRONG/CORRECT pairs, and the 16-item Review Checklist acts as a strong end-state validation checkpoint. Not 5 because there is no explicit validate→fix→retry feedback loop (e.g., after applying the restricted sandbox or testing the signed archive, no step says what to check or how to recover on failure); not 3 because checkpoints are more present than missing.

4 / 5

Progressive Disclosure

Clear overview structure with a linked table of contents, and detail is appropriately split: 'See references/browserenginekit-patterns.md for detailed layer hosting examples and transaction coordination' (and similarly for text interaction and downloads) points to a real, one-level-deep bundle file whose sections (XPC patterns, text input, layer hosting, scroll views, downloads, memory attribution) match the delegated topics, plus curated external doc links. Not 4 because navigation and signaling are clean with no orphan or nested references.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person imperative voice, explicit 'Use when...' triggers, and five concrete capability statements covering the framework's full scope. The only gap is a handful of natural synonyms (engine names like Gecko/Blink, regional phrasing) that would broaden trigger matching.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions: 'Build alternative browser engines', 'managing web content/rendering/networking extension processes', 'configuring GPU and networking process capabilities', 'checking alternative-engine device eligibility', and 'reviewing BrowserEngineKit entitlements and Info.plist setup' — comprehensive coverage of the framework's scope. Not 4 because no meaningful capability area is missing; the actions go beyond 'several specific actions with minor gaps'.

5 / 5

Completeness

Clearly answers both: what — 'Build alternative browser engines using BrowserEngineKit'; when — an explicit 'Use when developing a non-WebKit browser engine for iOS/iPadOS in supported regions, managing..., or reviewing...' clause with concrete trigger phrases. Not 4 because the 'when' is fully explicit and enumerated rather than merely present.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'browser engine', 'non-WebKit', 'iOS/iPadOS', 'entitlements', 'Info.plist', 'device eligibility'. Not 5 because a few natural synonyms are absent (e.g., engine names like Gecko/Blink/Chromium, 'EU browser', 'web content extension' phrasing users might use); not 3 because coverage is well beyond 'some relevant keywords with missing common variations'.

4 / 5

Distinctiveness Conflict Risk

'non-WebKit browser engine for iOS/iPadOS in supported regions' carves out a clear niche with distinct triggers (entitlement names, extension process types); minimal conflict risk with generic web development or WebKit skills. Not 4 because no closely related skill would plausibly collide on these triggers.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dpearson2699/swift-ios-skills

Path

skills/browserenginekit/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.