code-oss-logs

Find and read logs from Code OSS dev builds. Use when: finding logs, reading log files, debugging Code OSS, checking renderer logs, extension host logs, agent host logs, main process logs, investigating errors in dev builds.

Quality

100%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, actionable reference with executable commands, a clear directory map, a use-case routing table, and a well-sequenced probe workflow with an explicit cleanup checkpoint. It is well-organized into clearly navigable sections without requiring external bundle files.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no background on what logs or processes are — with every section (directory layout, use-case table, commands, tips) earning its place.	3 / 3
Actionability	Provides copy-paste-ready executable commands ("ls -lt ... \| head -5", "tail -50", "rg -n", "find ... -size +0") and an exact source edit for the forwarding flag, fully concrete rather than descriptive.	3 / 3
Workflow Clarity	Both the 4-step log-reading procedure and the 6-step console-forwarding workflow are clearly sequenced, with the fragile flag-toggle workflow including an explicit restore/cleanup checkpoint ("restore the flag... and remove every temporary console.log probe").	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single-file body is well-organized into clearly signaled sections, which satisfies the simple-skill exception for a 3.	3 / 3
	Total	12 / 12 Passed

Description

100%

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, concrete, and provides both a clear capability statement and an explicit, comprehensive trigger list. It is distinctively scoped to Code OSS dev-build logs with natural phrasing users would actually say.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ("Find and read logs from Code OSS dev builds") and enumerates specific log types, matching the multiple-concrete-actions anchor rather than the partial score-2 anchor.	3 / 3
Completeness	Explicitly answers what ("Find and read logs from Code OSS dev builds") and when via an explicit "Use when:" clause with concrete triggers, matching the score-3 anchor exactly.	3 / 3
Trigger Term Quality	Covers natural developer phrasing ("finding logs", "reading log files", "debugging Code OSS", "renderer logs", "extension host logs", "investigating errors") with strong breadth, matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to Code OSS dev builds with log-type-specific triggers, giving it a clear niche unlikely to conflict with generic skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: posit-dev/positron
Path: .github/skills/code-oss-logs/SKILL.md
Commit: b87c504

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