Name: appcircle
Rating: 60 (1 reviews)
Author: membranedev

appcircle

Appcircle integration. Manage data, records, and automate workflows. Use when the user wants to interact with Appcircle data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

82%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 content is a well-structured, highly actionable CLI integration guide with concrete commands and a clear connection-readiness workflow. Its main weaknesses are a couple of mild background asides and a dangling 'Step 2' reference that breaks the stated sequence.

Suggestions

Fix the dangling 'Step 2' reference by labeling the search/run sections as Step 2 or removing the cross-reference.

Trim the introductory Appcircle platform summary and the 'so you can focus on the integration logic' aside to tighten conciseness.

Consider moving the proxy flags table and the flat capability list into a short reference section to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven prose with only minor over-explanation (e.g. the opening 'Appcircle is a mobile CI/CD platform...' background and the 'so you can focus on the integration logic' aside), fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run, request) with flags and JSON-output examples covering the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connect-then-search-then-run sequence is clear with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but the dangling 'skip to Step 2' reference with no labeled Step 2 is a minor navigation gap, fitting 'clear sequence with most checkpoints present'.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references needed; the only gap is that the capability list and proxy-flag table are inlined rather than split out, fitting 'good structure; minor organization gaps'.	4 / 5
	Total	17 / 20 Passed

Description

57%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 distinctive thanks to the named product and includes an explicit trigger clause, but its capability phrasing is generic rather than concrete. Tightening 'Manage data, records, and automate workflows' into specific Appcircle actions would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Appcircle capabilities, e.g. 'Trigger builds, distribute to stores, and view test results'.

Add common user-facing synonyms or file/URL cues such as 'iOS/Android builds' or 'appcircle.io' to broaden trigger coverage.

Make the 'when' clause more specific, e.g. 'Use when the user wants to build, distribute, or inspect iOS/Android apps via Appcircle'.

Dimension	Reasoning	Score
Specificity	Names the Appcircle domain but the actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete capabilities like build, distribution, or store submission, matching the 'minimal or generic actions' anchor.	2 / 5
Completeness	It states both a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Appcircle data'); the 'when' is present but could be more specific, matching the 'has both what and when' anchor.	4 / 5
Trigger Term Quality	The primary natural trigger is the product name 'Appcircle' with 'interact with Appcircle data', but coverage lacks synonyms or common variations a user might say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The distinctive product name 'Appcircle' gives it a clear niche with minimal conflict risk, though the generic action phrasing leaves minor overlap with broad data-management skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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: membranedev/application-skills
Path: skills/appcircle/SKILL.md
Commit: f484c82

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.