AgentSkillsCN

article-authoring

在`content/**/article.md`中编写、编辑并组织Scribere文章。当您被要求创建新文章、修订文稿、调整前言（标题/摘要/标签/系列/状态）、添加素材与说明文字，或在遵循`docs/authoring.md`与`docs/article.md`的同时修复Lint问题时，可使用此技能。

SKILL.md
--- frontmatter
name: article-authoring
description: Write, edit, and structure Scribere articles in `content/**/article.md`. Use when asked to create a new article, revise prose, adjust frontmatter (title/summary/tags/series/status), add assets and captions, or fix lint issues while following `docs/authoring.md` and `docs/article.md`.

Article Authoring

Overview

This skill guides article creation and revision so the writing matches the project’s authoring rules, structure, and UK/AU spelling expectations. It treats articles as the primary source of visible content and keeps metadata strict and minimal.

Workflow

Start by reading the relevant specs: docs/authoring.md and docs/article.md. If the request affects templates or indexing, check docs/templating.md and docs/queries.md as well. Before making any changes, read AGENTS.md and follow it. It is the mandatory entry point for work in this repository.

When creating a new article, use npm run new to generate the content/YYYY/MM/DD/NN-slug/ folder and the initial article.md. If you already have a draft body, pipe it in with npm run new < draft.md. Use the body title as the source of truth for the folder name and frontmatter title, and keep the summary aligned with the article’s intent and audience.

When updating title, status, tags, or series, use npm run edit and follow the prompts. You can also pass an article path or published URL. If you want to replace the body, pipe it in with npm run edit < updated-body.md so the frontmatter and path remain stable.

When revising prose, keep paragraphs substantive, avoid contrast framing and rhetorical filler, and use UK/AU spelling. Preserve the author’s voice and focus on clarity, specificity, and readable structure, without introducing new jargon or template logic.

If linting is requested, run npm run lint -- --all (or use the repository’s lint command as given). Address warnings directly in the text. When lint is not requested, still avoid the patterns flagged in docs/authoring.md and ensure summaries remain accurate and useful in index views.

When adding assets, keep them local to the article folder and use clear captions and alt text. Ensure all visible text remains in the Markdown body and keep metadata separate from narrative content.

Output checks

Confirm frontmatter is complete and valid, the body title matches the folder name, and the visible article content is only in Markdown. Verify links use the published /content/... paths and do not point to filesystem locations.