CtrlK
BlogDocsLog inGet started
Tessl Logo

yc-cli

Operator's guide to the YC CLI (`yc`) for the Gini batch demo — scoped to the yc commands the demo actually uses: the validated browser-forward login flow (tmux + browser_connect) and investor research against Bookface. Assumes yc is installed but NOT logged in yet. Load before staging or running the demo.

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced operator's guide with strong validation and recovery guidance. Its only weak spots are minor narrative redundancy and a large inline output template that could be split out.

Suggestions

Consolidate the logout guidance so it lives authoritatively in section 4 and is only cross-referenced from section 1 and the Don'ts, removing the repeated rationale.

Move the section 2a investor profile output template into a references file (e.g. references/investor-profile-template.md) and link to it, tightening the main body.

Trim demo-color framing phrases ('the flow we rehearsed to convergence', 'the demo's Step 5 trust beat') to keep the guide lean.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence — no explaining what a CLI is — with copy-paste code blocks; minor trimmable demo-color narrative ('the flow we rehearsed to convergence') and the logout guidance repeated across sections 1, 4, and Don'ts.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — install/path checks, tmux login sequence, `yc search ... --json`, `yc tools run`, and the logout pair — with clearly marked template placeholders for profile data.

5 / 5

Workflow Clarity

Login, install, and logout are explicitly numbered with validation checkpoints (confirm via `grep -i successful` / `yc me`, redirect-to-login check), error-recovery fallbacks, and a Don'ts checklist; the destructive logout enforces both steps every time.

5 / 5

Progressive Disclosure

No bundle files exist, so everything is inline; sections are well-organized and clearly headed, but the ~40-line investor profile output template in section 2a could arguably live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

73%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 precise, third-person description that clearly states what the skill does and when to load it, with a very distinct niche. It is slightly narrow in action coverage and trigger breadth, keeping it just short of the top anchors.

Suggestions

Add one or two more concrete actions (e.g. 'pull a fund's track record', 'verify auth with yc me') to broaden specificity beyond login + research.

Expand the 'when' clause with additional natural trigger phrases (e.g. 'Use when staging or running the Gini demo, or when the user asks to log in to yc or research an investor').

DimensionReasoningScore

Specificity

Names the domain (YC CLI) and two concrete action areas — 'the validated browser-forward login flow (tmux + browser_connect) and investor research against Bookface' — but coverage is limited to those two rather than comprehensive.

3 / 5

Completeness

Clearly answers 'what' (operator's guide scoped to login + investor research) and gives an explicit 'when' trigger — 'Load before staging or running the demo' — though the trigger is a single narrow condition rather than multiple phrases.

4 / 5

Trigger Term Quality

Includes concrete natural terms a user would say ('yc', 'login flow', 'investor research', 'Gini batch demo') though they are niche to this specific demo rather than broad synonyms.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to 'the yc commands the demo actually uses' for a named demo, giving it a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
Open-Curiosity/gini-agent
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.