skill-creator-proposals

Internal tool (not user-invocable). Called by meta-skill-creator's persist step and by `opensquilla meta accept` CLI (Phase 2) to manage `~/.opensquilla/proposals/`: write_proposal / list / accept. Returns JSON.

Quality

70%

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 ./src/opensquilla/skills/bundled/skill-creator-proposals/SKILL.md

Quality

Content

86%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 concise, well-structured, and actionable with concrete action signatures and a genuine validation checkpoint on the destructive accept path; only minor actionability and feedback-loop gaps prevent a top score.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or over-explanation of concepts Claude already knows; every line (action signatures, atomicity, fallback) earns its place.	5 / 5
Actionability	Provides concrete, executable-shaped action signatures with flags and return values plus a concrete atomicity mechanism (os.rename()), though it stops short of full copy-paste-ready command examples.	4 / 5
Workflow Clarity	A clear sequence with a real validation checkpoint (accept 'refuses if any gate failed unless --force', FULL_GATED runtime E2E baseline) and error containment via atomic rename, with only minor gaps in explicit error-recovery feedback loops.	4 / 5
Progressive Disclosure	A short, well-organized body (Actions / Atomicity / Fallback) with a single thin-script bundle and no external references needed, matching the simple-skill exception for clean structure.	5 / 5
	Total	18 / 20 Passed

Description

55%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 is specific and well-scoped to a distinct internal niche, but it lacks natural user-facing trigger phrases and an explicit 'Use when...' clause, reflecting its machine-invoked nature.

Suggestions

Add an explicit trigger clause (e.g. 'Use when persisting or accepting a meta-skill proposal candidate') even though the skill is not user-invocable, so the activation condition is unambiguous.

Briefly enumerate what each action accepts/returns (e.g. 'write_proposal takes skill-md + gate results, returns proposal_id') to close the minor specificity gaps.

Consider including common natural synonyms ('proposal', 'skill candidate', 'accept skill') so the description reads less like purely internal jargon.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('write_proposal / list / accept', 'manage ~/.opensquilla/proposals/', 'Returns JSON'), with only minor gaps in per-action input coverage.	4 / 5
Completeness	The 'what' is clear (manage proposals via write/list/accept), but there is no 'Use when...' clause and the 'when' is only implied via its callers, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	It is explicitly 'not user-invocable' and keyed on CLI/caller names ('opensquilla meta accept', 'write_proposal') rather than natural user phrases, so the natural trigger terms users would actually say are largely absent.	2 / 5
Distinctiveness Conflict Risk	A sharply scoped niche (opensquilla proposal CRUD) with distinct invocation triggers and minimal overlap with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/skill-creator-proposals/SKILL.md
Commit: 94ac35e

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