Name: combine
Rating: 59.2 (1 reviews)
Author: Prisma-Labs-Dev

Blog Docs Log inGet started

combine

API reference: Combine. Query for publishers, subscribers, operators, async data streams.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/combine/SKILL.md

Quality

Content

71%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.

The body is admirably lean and well-structured for a documentation-search skill, but it is light on actionable mechanics and references a file that is not present in the bundle. Adding a concrete search step and providing the referenced file would solidify it.

Suggestions

Provide the referenced `combine-index.md` (in ./references/) or remove the dangling reference so navigation targets exist.

Add a concrete search/lookup step (e.g. how to query the docs, or to grep the reference files) so the guidance is executable rather than high-level.

Add a brief instruction for the case where the docs do not contain an answer (e.g. say so and list closest related files) to complete the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or over-explanation of concepts Claude already knows; every line (overview, return format, file list) earns its place. Not below 5 because there is no unnecessary explanation to trim.	5 / 5
Actionability	It gives some concrete guidance (a structured return format and a named file to consult) but only a high-level 'Search these docs to answer questions' with no concrete search mechanism or steps. Not 4 because no executable instruction or specific procedure is provided; not 2 because the return-format spec and file reference are more than minimal hints.	3 / 5
Workflow Clarity	As a simple read-only skill the single action is fairly unambiguous and the two-step return format (Summary, File paths) gives a clear sequence; no validation is required for a non-destructive search. Not 5 because the workflow is minimal and lacks an explicit handling step for when docs do not contain the answer.	4 / 5
Progressive Disclosure	Sections are organized and there is a one-level reference to `combine-index.md`, but that referenced file is absent from the bundle (no references/ directory exists), leaving a dangling reference. Not 4 because the missing backing file is a real organization gap; not 2 because the inline content is short and well-sectioned rather than a monolithic wall.	3 / 5
	Total	15 / 20 Passed

Description

66%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.

The description is concise and domain-specific with good trigger vocabulary, but it lacks an explicit 'Use when...' clause, leaving the invocation context implicit and capping completeness. Adding trigger guidance would lift it from a solid mid-range result to a strong one.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks about Combine, publishers/subscribers, operators, or reactive async streams in Swift.'

Add a natural synonym or framing term (e.g. 'Combine framework' or 'Swift reactive programming') to broaden trigger coverage.

Consider naming a second concrete action beyond 'Query' (e.g. 'look up operators', 'trace subscription chains') to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the Combine domain and lists several concrete topic areas ("publishers, subscribers, operators, async data streams") under the action "Query", matching the 'lists several specific actions; minor gaps' anchor. Not 5 because it relies on a single verb applied to topics rather than multiple distinct actions; not 3 because coverage is broader than 1-2 actions.	4 / 5
Completeness	It clearly states what the skill does ("API reference: Combine. Query for...") but provides no "Use when..." clause, so the 'when' is only weakly implied; per the judging guidelines a missing explicit trigger caps completeness at 3. Not 4 because there is no explicit 'when' guidance at all.	3 / 5
Trigger Term Quality	Terms like "publishers, subscribers, operators, async data streams" are natural vocabulary a user would mention about Combine, giving good keyword coverage. Not 5 because common synonyms and variations (e.g. "Combine framework", "reactive", file extensions) are missing; not 3 because the included terms go beyond a single generic keyword.	4 / 5
Distinctiveness Conflict Risk	Naming the specific Combine framework with its operators gives it a clear niche with mostly distinct triggers. Not 5 because "async data streams" could overlap with RxSwift or general concurrency skills; not 3 because it is more specific than broad document/data skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Prisma-Labs-Dev/apple-skills
Path: skills/combine/SKILL.md
Commit: 4986260

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.