CtrlK
BlogDocsLog inGet started
Tessl Logo

polyrepo-boundaries

Decide which xberg-io repository owns a cross-repository fix or API, and coordinate compatible changes across Xberg, Alef, enterprise, crawler, LLM, and OCR repositories. Load when work spans sibling repos; do not use for a self-contained Xberg edit.

71

Quality

86%

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

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.

A tight, well-organized policy skill that gives concrete ownership and API-placement rules plus a sequenced cross-repo workflow. The main gap is the absence of an explicit validation feedback loop for the multi-repo publish workflow.

Suggestions

Add an explicit feedback loop for the cross-repo workflow, e.g. "If a dependent repo's verification fails, fix and re-verify it before updating consumers."

Include one short worked example of a cross-repo fix (e.g., an SSRF-policy change touching crawlberg and xberg) showing the identify→coordinate→verify→publish→update sequence end to end.

Clarify what "verify each repository independently" entails concretely (CI? tests? build?) so the checkpoint is unambiguous.

DimensionReasoningScore

Conciseness

Lean policy text with no padding or explanation of concepts Claude already knows; every line earns its place (e.g., per-repo ownership bullets, "Never include changes from two repositories in one commit").

5 / 5

Actionability

Provides concrete, specific directives ("Put SSRF protection at the component that performs the outbound request"; "Commit and publish the dependency before updating a consumer"), but as an instruction-only skill lacks worked examples that would push it to fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

The cross-repo fix workflow is sequenced (identify lowest owning layer → coordinate dependency/release order → verify each repository → publish dependency before updating consumer) with a verify checkpoint, but lacks an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references; content is organized into clear sections (Polyrepo boundaries, Ownership, API placement), meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

87%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 well-crafted description that concisely states the skill's purpose, scope, and explicit load conditions in third-person imperative voice. It clearly distinguishes itself from a generic Xberg-edit skill via concrete ownership triggers.

DimensionReasoningScore

Specificity

Lists concrete actions — "Decide which xberg-io repository owns a cross-repository fix or API" and "coordinate compatible changes" — across named repos, with only minor coverage gaps relative to the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Decide... and coordinate compatible changes") and when ("Load when work spans sibling repos; do not use for a self-contained Xberg edit") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural domain phrases like "cross-repository fix or API", "sibling repos", and "self-contained Xberg edit" give good keyword coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (xberg-io polyrepo ownership) with distinct positive and negative triggers, yielding minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xberg-io/xberg
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.