Name: f5-networks
Rating: 56.8 (1 reviews)
Author: membranedev

f5-networks

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

Quality

65%

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/f5-networks/SKILL.md

Quality

Content

67%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 a tightly structured, executable guide to the Membrane CLI workflow for F5, with concrete commands, a state-machine connection flow, and a feedback loop. Weaknesses are the unnecessary marketing intro, a misleading 'Popular actions' section, and slightly inconsistent step numbering.

Suggestions

Delete the introductory marketing paragraph about who uses F5 Networks; Claude already knows this and it adds tokens without guidance.

Make the 'Popular actions' section actually list common F5 actions (e.g. list/modify virtual servers, pools, pool members) instead of repeating the discovery command.

Fix the step numbering inconsistency between the 'Step 2' reference and the '1b' section label so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening marketing paragraph ('F5 Networks provides solutions for application security, delivery, and optimization...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready commands throughout (install, login, connection ensure, action run, proxy) plus a flags table, but the 'Popular actions' section is misleading — it only repeats the discovery command instead of listing actual actions.	4 / 5
Workflow Clarity	Clear sequenced workflow (install → auth → connect → wait → search → run) with state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-retry feedback loop; minor gap is the awkward step numbering ('Step 2' referenced but section labeled '1b').	4 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and no bundle files; over the 50-line simple-skill threshold so it does not qualify for the top anchor, but structure and placement are good.	4 / 5
	Total	15 / 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 clearly identifies the F5 Networks niche and includes an explicit 'Use when' trigger, satisfying both the what and when requirements. Its main weakness is generic action language ('manage data, records, automate workflows') and missing common F5 synonyms like BIG-IP or iRules.

Suggestions

Replace generic verbs with concrete F5 capabilities, e.g. 'Manage virtual servers, pools, and pool members; inspect BIG-IP/iRule configurations'.

Add natural trigger synonyms users actually say, such as 'BIG-IP', 'iRules', or 'F5 ASM/WAF'.

Tighten the 'when' clause to name specific tasks (e.g. 'Use when configuring F5 BIG-IP virtual servers, pools, or policies').

Dimension	Reasoning	Score
Specificity	Names the F5 Networks domain and lists actions ('Manage data, records, and automate workflows'), but the actions are generic and abstract rather than concrete like 'extract text' or 'fill forms'.	3 / 5
Completeness	Provides both a 'what' ('F5 Networks integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with F5 Networks data'), though the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes the primary keyword 'F5 Networks' but misses common variations and synonyms a user might say (BIG-IP, iRules, F5), matching the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	'F5 Networks integration' is a clear vendor niche with distinct triggers and minimal conflict risk, but the generic 'manage data, records' phrasing keeps it just below the top anchor.	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/f5-networks/SKILL.md
Commit: f484c82

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