技能 documentation-and-adrs
📦

documentation-and-adrs

内容修订 r2 安全 ⚙️ 外部命令

Document Decisions and Architecture Clearly

Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.

支持: Claude Codex Code(CC)
🥉 78 青铜

使用我的智能体安装

将此请求复制给你的智能体,其中包含权威 Skill 页面和清单。

智能体请求
Review the Skillstore skill "documentation-and-adrs" from https://skillstore.io/skills/addyosmani-documentation-and-adrs.md and its manifest at https://skillstore.io/api/skills/addyosmani-documentation-and-adrs/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

你的智能体仍应展示其计划,并按安全策略请求必要确认。

测试它

正在使用“documentation-and-adrs”。 We chose PostgreSQL over SQLite and MongoDB for a multi-user task application.

预期结果:

An ADR outline with status, context, relational data requirements, alternatives considered, the PostgreSQL decision, and operational consequences.

正在使用“documentation-and-adrs”。 Document a task creation endpoint that requires a title and returns an identifier.

预期结果:

API reference guidance covering the request fields, validation errors, authentication expectations, response details, and a short usage example.

正在使用“documentation-and-adrs”。 Create onboarding documentation for a project with a development server and test suite.

预期结果:

  • A README structure covering project purpose, setup, commands, architecture, and contribution practices.
  • A verification checklist for setup instructions, API documentation, known gotchas, and current agent rules.

安全审计

安全
v2 • 2026/9/19 打开版本化报告

All 28 external-command detections are Markdown examples or inline command references in SKILL.md, not executable behavior. The environment-file and system-reconnaissance detections also point to documentation examples, and no prompt injection or data-exfiltration intent was found.

1
已扫描文件
289
分析行数
0
复核项
0
已忽略误报
最新一次完成的静态与语义审计未检测到已确认的安全发现。这并不能证明该 Skill 没有副作用。
审计者: codex 查看审计历史 →
分享与引用此报告

分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据,不判断该 Skill 是否安全。

打开版本化报告
安全评估

复制报告链接

https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-documentation-and-adrs/security.svg)](https://skillstore.io/skills/addyosmani-documentation-and-adrs?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/addyosmani-documentation-and-adrs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-documentation-and-adrs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/addyosmani-documentation-and-adrs.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
学术引用 (APA · BibTeX · CFF)

APA 引用

addyosmani. (2026). documentation-and-adrs security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2

BibTeX 引用

@techreport{addyosmani-addyosmani-documentation-and-adrs-2026, author = {addyosmani}, title = {documentation-and-adrs security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "documentation-and-adrs security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-19" url: "https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2" identifiers: - type: other value: "skillstore:addyosmani-documentation-and-adrs:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore 评分

评分依据 证据置信度: 高
55
架构
85
可维护性
87
内容
67
社区
83
规范符合性

你能构建什么

Record an architecture decision

Create an ADR that compares options, explains trade-offs, records the selected approach, and preserves consequences for future maintainers.

Document a public API

Draft consistent API documentation covering inputs, outputs, errors, authentication expectations, and representative usage guidance.

Improve project onboarding

Build a practical README, changelog structure, and agent guidance so contributors can understand setup, architecture, conventions, and recent changes.

试试这些提示

Draft a simple ADR
Create a concise ADR for this decision: [decision]. Include context, selected approach, two alternatives, consequences, status, and date. Use clear headings.
Match repository conventions
Review the repository context I provide and identify its ADR location, file format, numbering pattern, and headings. Then draft an ADR for [decision] that follows those conventions.
Document a public API
Write documentation for this public API: [API details]. Cover parameters, return values, validation, authentication, errors, and one realistic example. State unknowns instead of inventing behavior.
Build a documentation system
Design a documentation update for [project]. Propose ADRs for durable decisions, README sections for onboarding, API reference coverage, changelog entries, agent guidance, and a verification checklist. Preserve existing conventions and identify missing evidence.

最佳实践

  • Provide repository conventions and factual project context before requesting documentation.
  • Document the reasoning, constraints, alternatives, and consequences instead of restating implementation details.
  • Review every generated command, example, link, and security statement against the current project.

避免

  • Do not invent repository conventions, API behavior, commands, or architectural constraints.
  • Do not create duplicate ADR numbering schemes or replace established project formats without evidence.
  • Do not use documentation as a substitute for implementation, testing, access control, or operational validation.

常见问题

What does this skill create?
It creates ADRs, API documentation, README structures, changelog guidance, and documentation plans for human and AI contributors.
Can it find the correct ADR format?
Yes, when you provide repository context. It can identify existing locations, naming patterns, file formats, and section headings.
Does it write files automatically?
No. It produces documentation content and recommendations. The surrounding agent must review and apply file changes.
Can it validate API behavior?
No. It can organize supplied API facts, but it cannot test endpoints or confirm undocumented implementation behavior.
Who benefits most from this skill?
Engineering leads, API maintainers, open-source maintainers, developer experience teams, and agents working in unfamiliar repositories.
How should generated documentation be reviewed?
Check decisions, commands, links, examples, security claims, project conventions, and dates against the current repository before publishing.

开发者详情

作者

addyosmani

许可证

MIT

Skillstore 修订

r2

版本提示

作者未声明版本。

引用

5d5054f8a23586f9b500fece1cb613a9dffc787b

维护新鲜度

2026/9/19

使用量

2 次下载 · 0 次浏览

文件结构

📄 SKILL.md