CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/markdown-authoring

Author high-quality Markdown documentation with deterministic structure, lint compliance, and CI integration. Use when writing README files, creating docs pages, fixing markdownlint failures, defining style rules, or wiring markdown checks into pre-commit and pipelines. Keywords: markdown, markdownlint, readme, docs, headings, lists, code fences, links, images, lint config, ci, documentation style.

95

1.00x
Quality

92%

Does it follow best practices?

Impact

97%

1.00x

Average score across 7 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-4/

Create a Markdownlint Configuration File

A team wants to enforce Markdown authoring standards across their repository. They need a .markdownlint.json configuration file that encodes the skill's four key anti-patterns as enforced rules:

  1. Code fences must have explicit language tags (no bare fences).
  2. Heading levels must not skip (sequential hierarchy required).
  3. List markers must be consistent (one style across the document).
  4. Rules must not be broadly disabled — only specific targeted rules can be configured.

Produce a .markdownlint.json configuration file that:

  1. Enables all rules by default ("default": true).
  2. Configures the rule that enforces language tags on fenced code blocks.
  3. Configures the rule that prevents heading level skips.
  4. Configures the rule that enforces consistent list marker style.
  5. Does not globally disable any rules.
  6. Is valid JSON that would be accepted by markdownlint-cli2.

Also produce a short markdownlint-notes.md file that explains why each rule was configured and which anti-pattern it prevents.

Produce two files:

  • .markdownlint.json — the linter configuration
  • markdownlint-notes.md — explanations for each rule configured

SKILL.md

tile.json