scan-new-specs
Redirect Documentation Scans to the Supported Workflow
Spec-triggered documentation created drafts for features that had not shipped. This retired skill explains the failure and directs users to release-gated alternatives.
使用我的智能体安装
将此请求复制给你的智能体,其中包含权威 Skill 页面和清单。
Review the Skillstore skill "scan-new-specs" from https://skillstore.io/skills/warpdotdev-scan-new-specs.md and its manifest at https://skillstore.io/api/skills/warpdotdev-scan-new-specs/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智能体仍应展示其计划,并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文,而不是读取完整页面时,请使用这些链接。
测试它
正在使用“scan-new-specs”。 Can I schedule scan-new-specs each day?
预期结果:
No. Keep this retired skill paused. Use missing_docs in drift-watch mode for release-triggered documentation checks.
正在使用“scan-new-specs”。 How should I document one newly shipped feature?
预期结果:
Invoke write-feature-docs directly and interactively. Confirm the shipped behavior before drafting documentation.
正在使用“scan-new-specs”。 Why was this workflow retired?
预期结果:
It reacted to merged specifications before release and drafted unnecessary or inaccurate documentation without checking documentation worthiness.
安全审计
安全All nine static findings are false positives caused by markdown backticks around identifiers, file paths, and skill names. SKILL.md contains no executable commands or prompt injection, and it explicitly prevents use of the retired workflow.
风险因素
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据,不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/warpdotdev-scan-new-specs/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/warpdotdev-scan-new-specs?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/warpdotdev-scan-new-specs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-scan-new-specs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/warpdotdev-scan-new-specs.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 引用
warpdotdev. (2026). scan-new-specs security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-scan-new-specs/audits/1BibTeX 引用
@techreport{warpdotdev-warpdotdev-scan-new-specs-2026,
author = {warpdotdev},
title = {scan-new-specs security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/warpdotdev-scan-new-specs/audits/1},
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: "scan-new-specs security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "warpdotdev"
date-released: "2026-09-18"
url: "https://skillstore.io/skills/warpdotdev-scan-new-specs/audits/1"
identifiers:
- type: other
value: "skillstore:warpdotdev-scan-new-specs:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中你能构建什么
Redirect a documentation maintainer
Identify the supported release-gated workflow before reviewing documentation gaps.
Guide a feature engineer
Choose the interactive write-feature-docs workflow for a shipped feature.
Retire scheduled automation
Confirm that existing scan-new-specs schedules must remain paused.
试试这些提示
Explain whether scan-new-specs is still supported and name its replacement.
I need to find documentation gaps after a release. Which supported workflow should I use?
Recommend the supported process for an engineer documenting one shipped feature interactively.
Review my planned scan-new-specs schedule and explain how to migrate it to release-triggered, worthiness-gated documentation checks.
最佳实践
- Keep every scan-new-specs schedule paused.
- Run documentation gap checks only after stable releases.
- Require concrete documentation-worthiness evidence before drafting.
避免
- Do not invoke scan-new-specs for active documentation work.
- Do not treat a merged specification as proof of shipped behavior.
- Do not draft documentation for every product change without review.
常见问题
Is scan-new-specs still supported?
What replaces this skill?
Why was the old workflow retired?
How are documentation candidates evaluated now?
Can engineers still request feature documentation?
Does this skill run commands or modify files?
开发者详情
作者
warpdotdev许可证
MIT
Skillstore 修订
r1
版本提示
作者未声明版本。
引用
3048858843112bfab1ffe43e9123fca923ff4bf6
维护新鲜度
2026/9/18
使用量
0 次下载 · 0 次浏览
文件结构
📄 SKILL.md