Name: typeflowai
Rating: 61.6 (1 reviews)
Author: membranedev

typeflowai

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

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.

The content is highly actionable with copy-paste CLI commands and a sensible sequenced workflow including a connection-state feedback loop. Its main weaknesses are minor redundancy/concept blurb affecting conciseness and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Move the detailed connection-state machine and the proxy flag reference table into separate one-level-deep reference files (e.g., references/connections.md, references/proxy.md) and link to them from SKILL.md.

Resolve the dangling 'skip to Step 2' reference by labeling the workflow steps explicitly (Step 1: connect, Step 2: discover/run actions) or removing the cross-reference.

Trim the redundant 'Popular actions' section (it restates 'Searching for actions') and the platform-purpose blurb to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with minimal concept padding, though minor trimmable bits remain (the sales/marketing platform blurb and the 'Popular actions' section that duplicates 'Searching for actions').	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end — install, login (including headless), connection ensure, action list/run, and request proxying with a full flag table — fitting the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The install → authenticate → connect → search → run sequence is clear and the connection section has an explicit poll/state feedback loop, but the dangling 'skip to Step 2' reference and loose 1a/1b numbering leave minor validation gaps.	4 / 5
Progressive Disclosure	Sections are well-organized with headers and no nested references, but no bundle/reference files exist and inlineable material (the proxy flag table, connection state machine, and a vague 'Popular actions' stub) is collapsed into one ~140-line SKILL.md rather than split into one-level-deep references.	3 / 5
	Total	16 / 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 third-person, names a distinct app niche, and includes an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It is held back by generic action verbs and thin trigger-term variation.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions specific to TypeflowAI (e.g., 'create interactive product demos, edit sections, and automate onboarding workflows').

Broaden trigger terms beyond 'interact with TypeflowAI data' to include natural user phrasings like 'product demos', 'interactive walkthroughs', or 'training materials'.

Dimension	Reasoning	Score
Specificity	Names the domain and a few actions ('Manage data, records, and automate workflows') but the verbs are generic ('manage', 'automate') rather than concrete, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with TypeflowAI data') are present, though the 'what' is somewhat generic, matching the 'has both what and when; when could be more specific' anchor.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with TypeflowAI data' surfaces the app name and 'data', but lacks common synonyms or file-extension-style variations, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The specific app name TypeflowAI gives a clear niche with a distinct trigger ('interact with TypeflowAI data') and minimal overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 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: membranedev/application-skills
Path: skills/typeflowai/SKILL.md
Commit: f484c82

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