code-oss-logs

Find and read timestamped process logs from Code OSS dev builds, including main.log, renderer.log, extension host logs, and agenthost.log. For bundles produced by Export Agent Host Debug Logs, use agent-host-logs.

Quality

76%

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 ./.github/skills/code-oss-logs/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.

A well-structured, actionable reference for locating and reading Code OSS dev logs, with concrete commands and a thoughtful console-forwarding workflow; main gap is the slightly open-ended log-selection step in the procedure.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, conveying domain-specific log layout without padding; only minor stretches (the large layout tree and a few Tips) could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands (ls -lt, tail -50, rg -n, find -size +0) and a concrete code-edit workflow for console forwarding, covering the common cases.	5 / 5
Workflow Clarity	The Procedure and Console Forwarding Workflow are clearly sequenced with a cleanup/restore checkpoint, but the main read procedure's step 4 ('Read the relevant log file(s) based on what the user is investigating') leaves the selection slightly open.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested or buried references and no unnecessary external files, though it is a single inline document slightly above the size where structure alone would warrant a 5.	4 / 5
	Total	17 / 20 Passed

Description

70%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 concrete, well-scoped description that names specific log files and cleanly separates itself from a sibling skill, but it omits any explicit 'Use when...' trigger guidance, which caps completeness.

Suggestions

Add an explicit trigger clause such as 'Use when debugging Code OSS or Agents app dev runs, or when the user asks to inspect dev-build logs.'

Include a few more natural user phrasings (e.g. 'dev build logs', 'Copilot agent logs') to broaden trigger-term coverage.

Name one or two additional concrete actions (e.g. 'search', 'filter') if they are intended capabilities, to lift specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Find and read') plus specific named artifacts ('main.log, renderer.log, extension host logs, and agenthost.log'), giving clear, concrete coverage rather than vague language.	4 / 5
Completeness	The 'what' is clear ('Find and read timestamped process logs from Code OSS dev builds'), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the second sentence is a routing exception, not a trigger.	3 / 5
Trigger Term Quality	Includes natural terms a developer would say ('process logs', 'Code OSS', 'logs') plus specific filenames, but lacks broader synonyms/common phrasings to reach comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Code OSS / Agents app dev-build logs) and explicitly disambiguates from the related 'agent-host-logs' skill, minimizing conflict risk.	5 / 5
	Total	16 / 20 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: 9bb0f27

Reviewed: about 22 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.