Index of every page on this site: llms.txt
All skills
injectivelabs avatar

/injective-docs-style

@6d68c2c
Run it yourself

Audit and report adherence to Injective's documentation standards

Use this Skill: https://skilld.dev/gh/injectivelabs/agent-skills/injective-docs-style

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈22 tokens for metadata: the name and description. ≈735 when used: this file. ≈45 more on demand in 1 file.

Description uses 1.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈88 characters, or 1.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Injective Documentation Style, Skill Guide

Injective provides extensive developer documentation that is available on https://docs.injective.network (for humans) and https://docs.injective.network/llms.txt (for robots). This skill is to assist authors working on Injective's developer documentation.

When to apply

  • When writing developer documentation for Injective
  • When writing developer documentation adhering to Injective's developer documentation standards

Activities

  • Always run: "Check documentation style"
  • Only run if explicitly requested: "Verify technical correctness"

1 - Check documentation style

Invoke the "devrel-docs-style" skill, and specify use of American English.

2 - Verify technical correctness

Invoke the "injective-mcp-servers" skill, and connect to the Injective Documentation MCP server.

Use this to validate technical correctness of all pages that were checked in the previous step "Check documentation style". Do so by:

  • Make a list of claims, based on the contents of the files
    • Identify any new claims made
    • Identify any existing claims modified or removed
  • For each claim, based on the Injective Documentation MCP server.
    • Find supporting evidence
    • Find contradicting evidence

Based on this, create a list of all the claims, for each claim:

  • short description: 6 to 12 words
  • quote: text of each claim made, verbatim, as found in file
  • location: file path relative to project dir, and a single line number or range of line numbers, e.g. ./foo/bar.md:123-125
  • likelihood of correctness:
    • at least 80% sure claim is correct -> "Likely correct"
    • less than 80% sure claim is correct -> "Maybe correct"
    • less than 80% sure claim is wrong -> "Maybe wrong"
    • at least 80% sure claim is wrong -> "Likely wrong"
  • rationale: reason for chosen likelihood of correctness

Use format: ./assets/claims-template.md

3 - Assemble report

  • Start with the report file output in the "Check documentation style" step
  • Append the result from the "Verify technical correctness" step
    • The "## Claims" section should be inserted right above the "## Reproducing this report" section
  • Write file to disk with the same filename

Related skills

  • devrel-docs-style
  • injective-mcp-servers

Use the injective-mcp-servers skill to connect to the Injective Documentation MCP.

Through this you may search/ consult existing Injective developer documentation. Use this to check for correctness of any technical terminology that is Injective-specific.

If these skills are not available, selectively run the following commands to install them:

npx skills add bguiz/devrel-agent-skills --skill devrel-docs-style
npx skills add InjectiveLabs/agent-skills --skill injective-mcp-servers

Prerequisites

  • Injective MCP server must be running
  • User prompts should be issued from an AI tool that is configured to talk to the Injective MCP server

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill is designed for auditing Injective documentation style and technical correctness. It is safe for its intended use, although it includes standard instructions for installing its own dependencies from GitHub repositories.

  • Socket1mo

    1 alert: gptAnomaly

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 6d68c2c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
activates_on
[
  "*.md",
  "*,mdx*",
  "*.txt"
]
uses
[
  "injective-mcp-servers",
  "devrel-docs-style"
]
metadata
{
  "author": "bguiz",
  "version": "0.0.0"
}

README badge

README badge for injectivelabs/agent-skills/injective-docs-style