Tessl • The management layer for AI agent skills

SkillPublic

appfire

Appfire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Appfire 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 delivers executable, well-structured guidance with a genuine error-recovery loop around connection states — clearly stronger than the bad examples. Its main deductions are the duplicated action-discovery section, the dangling "Step 2" cross-reference, and the absence of any concrete Appfire-specific action examples.

Suggestions

Fix the workflow numbering: label the sections (Step 1: connect, Step 2: discover actions, Step 3: run) or replace "skip to **Step 2**" with the actual section name "Searching for actions".

Merge the "Popular actions" section into "Searching for actions" and add one concrete instantiated example, e.g. `membrane action list --intent "list workflow executions" ...` with a sample result and the corresponding `action run` call.

Replace the bare "Appfire Overview" bullet list with one line per capability and what it covers, or drop it in favor of the concrete actions it should be advertising.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and tight, but the "Popular actions" section duplicates "Searching for actions" (same `action list` invocation), and the "Appfire Overview" bullet list adds no actionable content. Efficient with minor trims possible.	4 / 5
Actionability	Commands are concrete and copy-paste ready (install, login with headless completion, `connection ensure`, `action list/run`, `request` with a full flag table), but no example ever instantiates a real Appfire action ID or intent, leaving `<actionId>` and `--intent "QUERY"` abstract.	4 / 5
Workflow Clarity	The install→login→connect→discover→run sequence is clear with a strong feedback loop (poll with `--wait`, branch on READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with recovery steps). Not a 5 because "skip to Step 2" is a dangling reference — steps are never numbered, so the reader must guess what Step 2 is.	4 / 5
Progressive Disclosure	A single-file skill with well-organized sections and no bundle files to reference; the proxy flag table and auth flows are appropriately placed inline. Minor gaps: the placeholder-like "Appfire Overview" list sits at the top without purpose, and the ~140-line body exceeds the simple-skill exception.	4 / 5
	Total	16 / 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 correctly names the Appfire domain and includes an explicit 'Use when' clause, but the capability list is generic rather than concrete and trigger coverage relies solely on the brand name. It is serviceable but below the standard of the good examples, which enumerate specific actions and multiple trigger phrases.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete actions drawn from the body's own overview, e.g. "Run workflow executions, manage integrations and connections, and fetch audit logs for Appfire apps".

Broaden trigger terms beyond the brand name, e.g. "Use when the user mentions Appfire, Appfire apps (e.g. Portfolio for Jira, Timesheets), or wants to automate workflows across their Atlassian, Microsoft, or Salesforce app data".

Make the 'when' clause non-circular by describing the situations that call for it (managing Appfire app data, auditing, integrating) rather than restating 'interact with Appfire data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Appfire integration") but its actions — "Manage data, records, and automate workflows" — are generic labels rather than concrete operations, matching the anchor for minimal/generic actions.	2 / 5
Completeness	Both 'what' ("Appfire integration. Manage data, records, and automate workflows") and 'when' ("Use when the user wants to interact with Appfire data") are explicitly present, though the 'when' is circular and could be more specific.	4 / 5
Trigger Term Quality	"Appfire" is a natural trigger term and appears three times, but the description misses common variations and synonyms (specific Appfire app names, Atlassian marketplace, Jira/Confluence app management) that users would say.	3 / 5
Distinctiveness Conflict Risk	"Appfire" is a distinct brand trigger with minimal generic overlap, but since Appfire apps run on Atlassian, Microsoft, and Salesforce platforms, there is minor overlap risk with related platform skills.	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/appfire/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

appfire

Table of Contents

Is this your skill?