Name: akana-by-perforce
Rating: 61.6 (1 reviews)
Author: membranedev

akana-by-perforce

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

Quality

72%

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/akana-by-perforce/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 body is highly actionable with executable CLI commands and a well-structured connection workflow including state-based polling feedback loops. Its main weaknesses are a slightly padded intro and a broken "Step 2" cross-reference that hurts navigation.

Suggestions

Fix the "skip to Step 2" reference by labeling the destination section (e.g. "Step 2: Searching for actions") or removing the dangling reference.

Trim the opening paragraph ("Akana by Perforce is an API management platform. It helps enterprises...") since Claude can infer what the product is from the description and docs link.

Consider moving the detailed clientAction state/polling reference into a separate reference file so the core workflow stays scannable.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, a flags table, and state-handling bullets; the only over-explanation is the introductory paragraph describing what Akana is, which is minor padding Claude could infer.	4 / 5
Actionability	Provides copy-paste ready CLI commands for every stage (login, connection ensure, polling, action list/run, request) plus a flags table and a JSON --input example, fully covering the common cases.	5 / 5
Workflow Clarity	A clear install → authenticate → connect → poll → search → run sequence exists with state-based feedback loops (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but "skip to Step 2" references a Step 2 that is not labeled, a minor navigation gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no need for external bundle files for a CLI wrapper of this size; minor gaps are the inline detailed polling/state logic that could optionally live in a reference.	4 / 5
	Total	17 / 20 Passed

Description

62%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 cleanly answers both what and when with an explicit trigger tied to a specific product, but its action verbs are generic and it misses natural synonyms like "API management." Strengthening the concrete actions and trigger vocabulary would push it toward the top anchors.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete capabilities specific to Akana, e.g. "design, secure, publish, and monitor APIs."

Add natural trigger synonyms such as "API management", "APIs", or "Akana APIs" so users phrasing the request differently still match.

Tighten the "what" clause to list 2-3 specific Akana actions rather than abstract data-management verbs.

Dimension	Reasoning	Score
Specificity	Names the Akana domain and a few actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete, matching the anchor for 1-2 named actions with limited specificity.	3 / 5
Completeness	Provides both a clear "what" (integration that manages data, records, workflows) and an explicit "Use when..." trigger, but the "what" is somewhat generic so it sits at the anchor where "when" could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product keyword "Akana by Perforce" in the trigger clause, but lacks common synonyms or variations (e.g. "API management", "APIs"), fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The specific product name "Akana by Perforce" gives a clear niche with minimal conflict risk, though the generic "manage data, records" verbs create minor overlap with other data skills.	4 / 5
	Total	14 / 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/akana-by-perforce/SKILL.md
Commit: f484c82

Reviewed: 2 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.