Name: jp-funda
Rating: 63.2 (1 reviews)
Author: membranedev

jp-funda

JP Funda integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with JP Funda data.

Quality

75%

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

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 body is highly actionable with copy-paste commands and a clear sequenced workflow, supported by clean section organization. It loses points mainly on mild intro padding and the absence of explicit validation checkpoints and any reference-file split for the larger tables.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, but the intro ('JP Funda is a financial data and analysis platform...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are mild over-explanation that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (npm install, membrane login/search/connect/action run/request) plus a flag table and a JSON-input example, covering the common cases exactly as the 5 anchor requires.	5 / 5
Workflow Clarity	The flow is clearly sequenced (install → login → connect → discover actions → run → proxy) with intermediate feedback ('Take the connector ID from output.items[0].element?.id, then...'), but explicit validation checkpoints are largely absent; the core operations are read-only queries so the destructive-cap does not apply, placing it at 4 rather than 5.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references (no bundle files exist), but the sizable Popular actions table and proxy flag table are inlined in SKILL.md with no external reference split, so it is good-but-not-ideal structure at 4.	4 / 5
	Total	17 / 20 Passed

Description

67%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 covers what and when with a distinct named-product trigger, but its 'when' clause is generic and its trigger vocabulary lacks the synonyms users would naturally say. Capability listing is concrete but uses the generic verb 'manage'.

Suggestions

Replace the generic 'Manage Organizations, Pipelines, Users, Filters' with the actual concrete capabilities the skill exposes (e.g., retrieve securities reports by date, EDINET code, or securities code), which currently only appear in the body.

Expand the 'Use when...' trigger to mention natural terms users would say, such as 'Japanese securities reports', 'EDINET code', 'securities code (証券コード)', or 'filing reports'.

Reconcile the description's capability list (Organizations/Pipelines/Users/Filters) with the body, which is entirely about securities reports — the two describe different functionality.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ('Manage Organizations, Pipelines, Users, Filters'), though 'manage' is a generic umbrella that leaves minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	It states both a clear 'what' (manage Organizations, Pipelines, Users, Filters) and an explicit 'when' ('Use when the user wants to interact with JP Funda data'), but the 'when' clause is generic rather than concrete, so it sits at 4 and not the fully-explicit 5.	4 / 5
Trigger Term Quality	The only natural trigger is the product name 'JP Funda' in 'interact with JP Funda data'; it misses common variations or synonyms a user might say (Japanese stocks, securities reports, EDINET, filings), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product 'JP Funda' gives it a clear niche with minimal conflict risk, but the generic capability nouns (Organizations, Pipelines, Users, Filters) carry minor overlap risk with other integration skills, fitting 4 rather than a clean 5.	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/jp-funda/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.