CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linkedin-reader

Read LinkedIn for financial research through opencli: the user's feed, and job search with location, seniority, job type, remote, company, and date filters. Use this skill whenever the user wants to check their LinkedIn feed, see what professionals or analysts are posting about a company, market, or earnings, gauge professional sentiment, or search finance and trading jobs on LinkedIn. Read-only: it cannot post, like, comment, connect, message, or apply.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, highly actionable skill body with a clear five-step workflow, pre-flight validation, and error recovery, held back mainly by redundant content. Consolidating the duplicated setup/error tables and the repeated `opencli doctor` explanations would lift both conciseness and progressive disclosure.

Suggestions

Merge the 'Common setup issues' table (Step 1) with the 'Error Reference' table at the end — three of four rows are duplicates; keep one canonical table and point to it from the other section.

Fold Step 5 (Diagnostics) into the doctor coverage in Step 1 or the Error Reference, since `opencli doctor` and what it checks are explained twice.

Move the detailed extension-installation steps out of SKILL.md into references/commands.md (where they already appear) and keep only a one-line pointer plus the verify command in the body, reducing token cost and the duplication across files.

DimensionReasoningScore

Conciseness

The body is mostly lean tables and commands, but contains genuine redundancy: the "Common setup issues" table and the "Error Reference" table repeat three of four rows (Extension not connected, No session, AuthRequiredError), and `opencli doctor` is explained in both Step 1 and Step 5. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level 4.

3 / 5

Actionability

Commands are copy-paste ready and cover the common cases — `opencli linkedin timeline --limit 20 -f json`, `opencli linkedin search "portfolio manager" --location "New York" --limit 15 -f json`, `--details` for full listings — plus an install command, a format-flag table, and named output columns, matching the fully-executable top anchor.

5 / 5

Workflow Clarity

The five-step sequence (setup → identify → execute → present → diagnostics) has explicit validation and feedback loops: a pre-flight probe branching on READY/NOT_INSTALLED/SETUP_NEEDED, the rule "run `opencli doctor` before any other command if unsure", and an error table with fixes for retry. As a read-only skill, the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

`references/commands.md` is a real, well-signaled, one-level-deep reference with clear guidance on when to read it, and the body is a reasonable overview. However, the setup and extension-install content is duplicated between SKILL.md and references/commands.md rather than split, a minor organization gap that keeps this just below the top anchor.

4 / 5

Total

17

/

20

Passed

Description

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

An excellent description: concrete capabilities, explicit 'Use this skill whenever...' triggers with natural user phrasing, third-person voice, and a clearly bounded read-only scope. It matches the rubric's good examples in both structure and quality.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — reading the user's feed and job search with named filters ("location, seniority, job type, remote, company, and date filters") — and exhaustively enumerates the read-only boundary ("it cannot post, like, comment, connect, message, or apply"), matching the comprehensive-coverage anchor. It is written in third person, so no voice penalty applies.

5 / 5

Completeness

Both 'what' and 'when' are explicit: capabilities are stated concretely and the clause "Use this skill whenever the user wants to check their LinkedIn feed... gauge professional sentiment, or search finance and trading jobs" provides concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

It includes the natural phrases a user would actually say: "check their LinkedIn feed", "see what professionals or analysts are posting about a company, market, or earnings", "gauge professional sentiment", and "search finance and trading jobs". Synonym coverage is strong (feed/posts, professionals/analysts, market/earnings), matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (LinkedIn reading via opencli for financial research) with distinct triggers (LinkedIn feed, professional sentiment, finance/trading jobs) and an explicit read-only scope, so conflict with other skills is minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

himself65/finance-skills

Path

plugins/social-readers/skills/linkedin-reader/SKILL.md

Reviewed

Table of Contents

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.