push

Commit and push vault changes to Git with smart commit messages. Auto-stages files, creates meaningful commits, and syncs with remote. Use after making vault changes or at end of day.

Quality

75%

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 ./vault-template/.claude/skills/push/SKILL.md

Quality

Content

65%

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

The body is actionable with copy-paste git commands and good organization, but suffers from duplicated sections and lacks embedded validation checkpoints for the risky push flow. With no bundle files, it is monolithic rather than progressively disclosed.

Suggestions

Collapse the duplicated staging/commit/push steps — keep one canonical command sequence and remove the restated 'What This Skill Does' and 'Workflow Integration' restatements.

Embed validation as checkpoints in the standard flow (e.g. 'after git add, confirm staged files; if force push requested, require explicit confirmation') with a fix-and-retry loop.

Move troubleshooting and workflow-integration recipes into separate reference files (e.g. TROUBLESHOOTING.md) referenced from the body to reduce inline length.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete examples, but 'What This Skill Does' and 'Workflow Integration' restate the frontmatter and the Git Operations flow, and 'Handles merge conflicts gracefully' is unsupported padding, so it does not meet the 'every token earns its place' bar.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (git add/commit/pull --rebase/push), concrete .gitignore contents, and troubleshooting commands like git init and git remote add.	3 / 3
Workflow Clarity	The standard flow is sequenced and safety checks are listed, but for a destructive/batch push operation the validation is a separate menu rather than explicit verify-then-proceed checkpoints with a fix-and-retry feedback loop, capping it below 3.	2 / 3
Progressive Disclosure	Well-organized into clear sections, but with no bundle files present everything lives inline in a ~148-line SKILL.md, so content that could be split out (troubleshooting, integration recipes) is not separated into one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 strong, third-person description that concretely names its actions and includes an explicit usage trigger. Trigger-term coverage is the weakest dimension because it leans on vault-specific phrasing rather than broader natural language users would say.

Suggestions

Broaden trigger terms to common phrasings users would actually say, e.g. 'git push', 'save my notes', or 'sync my vault to remote'.

Consider dropping the buzzwordy 'smart' in 'smart commit messages' in favor of a concrete descriptor like 'auto-generated from the diff'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Commit and push vault changes', 'Auto-stages files', 'creates meaningful commits', 'syncs with remote' — matching the anchor for several specific actions rather than a vague domain.	3 / 3
Completeness	Explicitly states both what it does and when to use it via 'Use after making vault changes or at end of day', satisfying the anchor that requires an explicit when-clause.	3 / 3
Trigger Term Quality	Includes some natural terms ('push', 'commit', 'vault changes', 'end of day') but relies on product-specific 'vault' phrasing and lacks common variations like 'save my changes' or 'git push', so coverage is not comprehensive.	2 / 3
Distinctiveness Conflict Risk	The vault/notes git-sync niche is clear and the triggers ('vault changes', 'end of day') are specific enough to avoid overlap with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: ballred/obsidian-claude-pkm
Path: vault-template/.claude/skills/push/SKILL.md
Commit: ef1e4da

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