docs-validating-software-engineering-separation

docs-validating-software-engineering-separation is a skill for Claude Code, Codex from wahidyankf/ose-public. It costs 62 tokens per session (993 once invoked), scanned A, original, MIT.

A documentation review guide for keeping repository-specific style instructions separate from educational material. It also checks that prerequisites and links are stated correctly.

In plain words
What is it for?
Use it to review files under repository documentation and educational-content areas, check prerequisite statements, and validate that style guides describe local conventions rather than general lessons.
Why use it?
It prevents duplicate or misplaced explanations and helps readers know what they must understand first. It also catches separation and relationship errors in documentation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to review files under repository documentation and educational-content areas, check prerequisite statements, and validate that style guides describe local conventions rather than general lessons.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wahidyankf/ose-public/docs-validating-software-engineering-separation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add wahidyankf/ose-public --skill docs-validating-software-engineering-separation
Clone the repo
git clone --depth 1 https://github.com/wahidyankf/ose-public

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for docs-validating-software-engineering-separation

README.md
[![agentmods](https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-validating-software-engineering-separation/github.svg)](https://agentmods.dev/skills/wahidyankf/ose-public/docs-validating-software-engineering-separation)
Your own site
<a href="https://agentmods.dev/skills/wahidyankf/ose-public/docs-validating-software-engineering-separation"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-validating-software-engineering-separation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for docs-validating-software-engineering-separation

Your own site · 80×15
<a href="https://agentmods.dev/skills/wahidyankf/ose-public/docs-validating-software-engineering-separation"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-validating-software-engineering-separation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 993 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00993
Opus 5.5 $0.00025 $0.00397
Sonnet 5.5 $0.00012 $0.00199
Haiku 4.5 $0.00006 $0.00099

Measured 2d ago against content hash 13d4d6364fa4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-validating-software-engineering-separation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/docs-validating-software-engineering-separation/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Validating Software Engineering Documentation Separation

This Skill provides comprehensive guidance for validating the separation between repository-specific style guides (docs/explanation/software-engineering/) and educational content (apps/ayokoding-www/), as defined in the Programming Language Documentation Separation Convention.

Purpose

Use this Skill when:

  • Implementing style guide separation validation in checker agents
  • Validating docs/explanation content doesn't duplicate AyoKoding educational content
  • Ensuring prerequisite knowledge statements exist and are correct
  • Checking style guides focus on repository-specific conventions only
  • Understanding content separation patterns

Validation Scope

Lifecycle Delegation

No declared gate validates internal links, so path and fragment checks stay here alongside the semantic correctness of prerequisite relationships and all separation checks. ./rhino md internal-link validate (on demand) reports missing target files but does not check #fragment anchors.

CRITICAL: Only validate relationships explicitly listed in the Software Design Reference prerequisite table.

Authoritative Source: Software Design Reference - Specific Prerequisites

Current explicit relationships to validate:

  1. docs/explanation/programming-languages/golang/ ↔ ayokoding-web/.../golang/
  2. docs/explanation/programming-languages/elixir/ ↔ ayokoding-web/.../elixir/

DO NOT validate languages/frameworks not in this table (TypeScript, Python, etc.) until they are explicitly added to the Software Design Reference.

Core Validation Principle

CRITICAL: docs/explanation/ content MUST NOT duplicate AyoKoding educational content.

Separation Pattern:

  • AyoKoding = Educational (language syntax, by-example tutorials, generic patterns)
  • docs/explanation/ = Style guides (OSE Platform naming, framework choices, repository patterns)

Read the full file on GitHub · 113 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 113 lines · 62 tokens per session scan A 13d4d6364fa4

Subscribe to this mod's changes

docs-validating-software-engineering-separation is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 993 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.

Related

Other skills, from other repositories

gpu-document-processing

Use when processing large PDFs, document collections, or bulk text extraction tasks that benefit from GPU-accelerated processing. Triggers when the user provides large documents or needs bulk document analysis.

langchain-ai/deepagents · 41 tokens

enrich-excel

Enrich a live Excel spreadsheet by researching missing data with TinyFish and writing results directly into the running Excel app via AppleScript. Use when a user says "fill in my spreadsheet", "enrich this Excel file", "research and fill missing data", "update my Excel sheet", "look up data for each row", or any…

tinyfish-io/tinyfish-cookbook · 92 tokens

azure-ai-document-intelligence-ts

Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu...

benjaminasterA/antigravity-awesome-skills · 45 tokens

nx-plugin-for-aws

Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.

awslabs/nx-plugin-for-aws · 46 tokens

document-parsing

Extract readable Markdown from local Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and text-based PDF files using the preinstalled AnyDoc runtime.

Cloudgeni-ai/opengeni · 39 tokens

opengeni-documents

Create, inspect, edit, review, import, and export durable Opengeni document artifacts and explicit DOCX file boundaries. Use when creating or editing a document Artifact or DOCX (reports, briefs, proposals, forms, tables, sections, headers, footers, comments, tracked changes, and Word-compatible delivery); ordinary…

Cloudgeni-ai/opengeni · 78 tokens