Name: northflank
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

northflank

Northflank integration. Manage Projects, Users, Teams. Use when the user wants to interact with Northflank data.

Quality

67%

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

Quality

Content

65%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 copy-paste CLI commands across the full workflow, but it is held back by conversational padding, a duplicated action-discovery section, an undefined 'Step 2' reference, and the absence of validation guidance for destructive proxy requests.

Suggestions

Remove marketing-style and conversational filler (the platform intro, 'focus on the integration logic rather than auth plumbing', 'burn less tokens') to tighten conciseness.

Define the referenced 'Step 2' or remove the dangling cross-reference, and merge the redundant 'Searching for actions' and 'Popular actions' sections.

Add a validation/verification checkpoint for destructive proxy requests (e.g., 'Confirm the target resource before running DELETE/PATCH; verify the response status and re-fetch to confirm the change').

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight, useful code blocks, but it includes several instances of unnecessary padding such as the marketing-style intro ('a unified DevOps platform that simplifies infrastructure management...'), 'so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens', and the vague filler 'Use action names and parameters as needed.'	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every common case — install, login, connection ensure, state polling, action list/run, and proxy requests — with real flags and a clear options table, covering the common cases comprehensively.	5 / 5
Workflow Clarity	The connection workflow has a state-machine sequence with polling and feedback loops, but it references a 'Step 2' that is never defined, and the proxy section enables destructive HTTP methods (e.g., DELETE) with no validation or verification guidance, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	It is a single flat ~150-line file with clear section headers but no external references, a redundant near-duplicate action-list section ('Searching for actions' vs 'Popular actions'), and a broken 'Step 2' cross-reference, leaving it between adequate and good organization.	3 / 5
	Total	14 / 20 Passed

Description

70%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.

A solid description that names the domain, lists concrete entities, and includes an explicit 'Use when' trigger. It is held back from the top tier by relying on one generic action verb ('Manage') and generic entity nouns rather than richer, more specific trigger phrasing.

Suggestions

Replace the single verb 'Manage' with several specific actions (e.g., 'Create and manage Projects, invite Users, and organize Teams') to raise specificity.

Expand the trigger clause with concrete natural phrases a user would say (e.g., 'Use when the user wants to manage Northflank projects, teams, users, or services').

Add domain-specific synonyms or service names (e.g., 'Services', 'Deployments', 'Addons') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Northflank domain and the concrete action 'Manage' applied to 'Projects, Users, Teams', but relies on a single generic verb rather than enumerating several specific operations, matching the anchor for 1-2 concrete actions that are not comprehensive.	3 / 5
Completeness	Provides both a 'what' ('Manage Projects, Users, Teams') and an explicit 'Use when' trigger clause ('Use when the user wants to interact with Northflank data'); the 'when' is present and clear but could be more specific with concrete trigger phrases, so it sits just below the top anchor.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('Northflank', 'Projects', 'Users', 'Teams') and an explicit trigger ('interact with Northflank data'); good coverage, though a few common synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	The proper noun 'Northflank' gives it a clear niche with minimal conflict risk, but the entity nouns ('Projects, Users, Teams') are generic and could overlap with adjacent DevOps/platform skills, keeping it just below the fully-distinct anchor.	4 / 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/northflank/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.