Name: the-things-network
Rating: 55.2 (1 reviews)
Author: membranedev

the-things-network

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

Quality

63%

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/the-things-network/SKILL.md

Quality

Content

68%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 commands and a well-structured connection state machine, but it carries some unnecessary background explanation and lacks validation checkpoints for destructive proxy operations.

Suggestions

Trim the opening overview paragraph and the "focus on integration logic rather than auth plumbing" commentary that Claude does not need.

Add a validation/checkpoint step before destructive proxy requests (e.g., confirm the method and target with the user before DELETE/POST) so workflow clarity is not capped.

Fix the inconsistent step labeling ("1b" and "Step 2" appear without a labeled Step 1/2) so the connection sequence reads as a coherent numbered workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening TTN overview (LoRaWAN, smart cities, agriculture) and phrasing like "so you can focus on the integration logic rather than auth plumbing" explain context Claude does not need and could be tightened.	3 / 5
Actionability	Every section provides copy-paste-ready commands with explicit flags — `membrane login`, `connection ensure`, `action run --input`, and a full proxy-request flag table — covering the common cases fully.	5 / 5
Workflow Clarity	The connection flow has a clear state machine with polling and a READY/BUILDING feedback loop, but the proxy section exposes destructive methods (DELETE) and batch action runs with no validation or verification checkpoint, capping this dimension per the destructive-operations rule.	3 / 5
Progressive Disclosure	No bundle files exist, and the single SKILL.md is organized into clear, well-labeled sections with no nested references; the inline proxy-flag table is the only borderline reference material that could live in a separate file.	4 / 5
	Total	15 / 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 has an explicit trigger clause and a distinct named-product niche, but its capability description is generic ("manage data, records, and automate workflows") rather than concrete.

Suggestions

Replace generic verbs with concrete TTN-specific actions (e.g., "List end devices and applications, send downlinks, query uplink messages").

Add natural synonyms and file-format/protocol triggers users might say (LoRaWAN, IoT, TTN, end devices, gateways).

Tie the "when" clause to specific intents like joining devices, reading uplink data, or sending downlinks rather than the vague "interact with data".

Dimension	Reasoning	Score
Specificity	The domain (The Things Network) is named, but the listed actions — "Manage data, records, and automate workflows" — are generic abstractions rather than concrete capabilities, matching the anchor that names the domain with minimal/generic actions.	2 / 5
Completeness	Both a "what" (integration that manages data/records/workflows) and an explicit "when" ("Use when the user wants to interact with The Things Network data") are present, but the "what" is generic rather than concrete, so it stops short of a 5.	4 / 5
Trigger Term Quality	"The Things Network" is a relevant keyword and the "Use when... interact with The Things Network data" clause is a natural trigger, but common synonyms users might say (LoRaWAN, IoT, TTN) are missing, matching the anchor with relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	The trigger is tied to a specific named product (The Things Network), giving it a clear niche and low conflict risk, though the generic action verbs ("manage data, records") leave minor overlap with other data-integration 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/the-things-network/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.