Name: falcosecurity
Rating: 52.8 (1 reviews)
Author: membranedev

falcosecurity

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

Quality

59%

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

Quality

Content

61%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 concrete Membrane CLI commands and a sensible connection-state workflow, but it is held back by concept over-explanation and the absence of validation around destructive proxy operations. Structure is good overall with a few dangling references.

Suggestions

Trim the Falco overview paragraph and auth-plumbing commentary to assume Claude's knowledge of what Falco is.

Add an explicit validation/verification checkpoint before and after destructive proxy requests (POST/PUT/PATCH/DELETE), e.g., confirming the target connection ID and checking the response status.

Resolve the dangling "skip to Step 2" reference and either populate or remove the empty Overview bullets (Rule Groups, Configuration Options).

Dimension	Reasoning	Score
Conciseness	Most of the body is lean, command-driven CLI usage, but the opening Falco overview ("Falco acts like a security camera for your Kubernetes infrastructure") and phrases like "so you can focus on the integration logic rather than auth plumbing" explain concepts or add marketing fluff Claude does not need.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request) plus a flags table, with only minor gaps such as unspecified real action IDs or Falco endpoints.	4 / 5
Workflow Clarity	The install → authenticate → connect → search → run sequence is clear and includes polling/feedback for connection states, but the proxy section exposes destructive methods (DELETE, PUT, PATCH) with no validation or verification checkpoint, which caps this dimension at 3.	3 / 5
Progressive Disclosure	The body is well organized into clearly headed sections and needs no external bundle files for its self-contained CLI guidance, though the empty "Falcosecurity Overview" bullets (Rule Groups, Configuration Options) and the dangling "skip to Step 2" reference are minor organization gaps.	4 / 5
	Total	14 / 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 pairs a what-statement with a Use-when trigger in third person, but its action list is generic and it lacks Falco-specific trigger synonyms. It is clearly distinct as a product integration yet could be sharpened considerably.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete Falco-specific actions (e.g., inspect runtime security events, manage detection rules, review alerts).

Add natural trigger synonyms users would say, such as "Falco", "runtime security", or "Kubernetes security threats".

Make the Use-when clause more specific by naming real use cases (e.g., querying alerts or managing Falco rules) rather than the circular "interact with Falcosecurity data".

Dimension	Reasoning	Score
Specificity	It names the domain ("Falcosecurity integration") but the listed actions — "Manage data, records, and automate workflows" — are generic rather than concrete Falco-specific operations, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It provides both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when the user wants to interact with Falcosecurity data" trigger, though the "when" clause is somewhat generic and could name concrete use cases.	4 / 5
Trigger Term Quality	It includes the product name "Falcosecurity" twice but misses common variations and synonyms a user would naturally say ("Falco", "runtime security", "Kubernetes security threats"), so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Falcosecurity gives it a clear niche with minimal conflict risk, but the generic "manage data, records" phrasing leaves 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/falcosecurity/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.