Name: recorded-future
Rating: 66.4 (1 reviews)
Author: membranedev

recorded-future

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

Quality

80%

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

Quality

Content

82%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 skill body is a well-structured, highly actionable guide to driving Recorded Future via the Membrane CLI, with copy-paste commands and a clear connection workflow. Its main weaknesses are a few over-explained passages Claude already knows and the absence of explicit validation/feedback loops for destructive or batch actions.

Suggestions

Trim the introductory paragraph explaining what Recorded Future is as a product; Claude already knows this and it costs tokens.

Add an explicit validation checkpoint when running actions or proxy requests (e.g. check the response 'output'/'error' field and retry on auth or transient failures) to support batch/destructive operations.

Consider moving the full proxy flag reference table into a references file and keeping only the most common flags inline, to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and instruction-focused with executable bash commands, but includes some over-explanation Claude already knows (e.g. 'Recorded Future is a threat intelligence platform that collects and analyzes information from the web...') that could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready membrane commands with flag tables (e.g. 'membrane action run <actionId> --connectionId=... --input ...' and the proxy flag table) covering the common interaction cases.	5 / 5
Workflow Clarity	The connection setup has a clear sequenced flow with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop, but there is no explicit validate/fix/retry feedback loop for the run/proxy actions, leaving a minor validation gap.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with appropriate overview-level depth and no nested references, though it inlines some reference-style detail (e.g. the full proxy flag table) that could live elsewhere.	4 / 5
	Total	17 / 20 Passed

Description

78%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 concise, third-person, and clearly identifies a distinct Recorded Future niche with an explicit 'Use when' trigger clause. It is strong overall, with room to sharpen the 'when' clause and broaden natural trigger synonyms to reach a perfect score.

Suggestions

Broaden the 'when' clause with concrete trigger terms users would naturally say, e.g. 'Use when working with Recorded Future threat intelligence, risk rules, vulnerabilities, or attack-surface data.'

Make the capability list more comprehensive (e.g. 'query intelligence lists, run risk rules, fetch vulnerability and attack-surface reports, automate workflows') to approach full coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' which names the Recorded Future domain plus several concrete capability families (data/records management, workflow automation), with minor gaps in coverage.	4 / 5
Completeness	It explicitly answers 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Recorded Future data'); the 'when' is explicit but somewhat generic, sitting just below the 5 anchor.	4 / 5
Trigger Term Quality	The trigger clause 'Use when the user wants to interact with Recorded Future data' surfaces the natural keyword the user would say ('Recorded Future data'), though it lacks synonyms or file extensions that would lift it to 5.	4 / 5
Distinctiveness Conflict Risk	The 'Recorded Future' niche is a clear, named product domain with distinct triggers, so it is unlikely to fire for unrelated skills and has minimal conflict risk.	5 / 5
	Total	17 / 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/recorded-future/SKILL.md
Commit: f484c82

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