CtrlK
BlogDocsLog inGet started
Tessl Logo

docs

Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `.agents/docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.

75

Quality

92%

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

85%

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

A well-organized, instruction-only skill with concrete placement rules, a sequenced drift-prevention workflow, and explicit validation checkpoints. Its main weakness is repeating the same four-path scope across three sections, which slightly dilutes token efficiency.

Suggestions

State the four in-scope paths once in the Scope section and have the intro and Working Rule 1 refer back to it, instead of restating the full path list three times.

Consider collapsing the intro paragraph into a single sentence since its content largely duplicates the Scope and Working Rules sections.

Trim the writing-style bullet's list of AI-writing tells or move it behind a one-level reference to the doc-author overlay to keep the body leaner.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the four-path scope ("`docs/core-concepts/`, `.agents/docs/`, `docs/sdks/`, and `openapi/`") is restated in the intro, the Scope section, and again in Working Rule 1, which could be tightened. It is efficient but includes unnecessary repetition.

2 / 3

Actionability

Gives concrete, executable guidance: exact folder paths, a concrete file convention ("`architecture.md` file inside the relevant `docs/core-concepts/<domain>/` folder"), and specific per-surface placement rules, which is actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Working Rule 3 sequences drift prevention (check docs before changing implementation; update Markdown and OpenAPI YAML in the same pass; then conditional updates per affected surface) and the Validation section provides explicit cross-check checkpoints before finishing.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external bundle references, and content is well-organized into clear Scope, Working Rules, and Validation sections; the single cross-reference to the doc-author skill's `INSFORGE.md` overlay is clearly signaled and one level deep.

3 / 3

Total

11

/

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 specific, trigger-driven, and well-scoped to a concrete documentation surface within a named repository. It cleanly answers what and when without verbosity.

DimensionReasoningScore

Specificity

Enumerates concrete editing targets — "public docs in `docs/core-concepts`", "agent docs in `.agents/docs`", "SDK integration guides in `docs/sdks`", and "OpenAPI specs in `openapi`" — naming multiple specific surfaces rather than vague language.

3 / 3

Completeness

Answers both what (editing/contributing to product documentation across four surfaces) and when via the explicit "Use this skill when contributing to InsForge's product documentation in this repository" trigger clause.

3 / 3

Trigger Term Quality

Uses natural terms a maintainer would say — "documentation", "docs", "SDK integration guides", "OpenAPI specs" — with good coverage of the domain's common phrasings.

3 / 3

Distinctiveness Conflict Risk

Scoped to InsForge's repository documentation in specific folders, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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
InsForge/InsForge
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.