gpt-series-reasoning-style
Verify AI Deliverables with Evidence
AI work can appear complete before the result is opened, tested, or checked against the request. This skill adds staged planning, real-environment verification, and honest completion levels.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "gpt-series-reasoning-style" from https://skillstore.io/skills/jadeyingwah-gpt-series-reasoning-style.md and its manifest at https://skillstore.io/api/skills/jadeyingwah-gpt-series-reasoning-style/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「gpt-series-reasoning-style」を使用しています。 Build a small dashboard and tell me when it is finished.
期待される結果:
The dashboard is implemented. I opened it in the target environment, checked the main interaction, and verified the displayed totals. Mobile layout and external data refresh remain unverified.
「gpt-series-reasoning-style」を使用しています。 Have two agents research and implement this feature.
期待される結果:
- Research agent: documented assumptions and acceptance checks.
- Implementation agent: completed the feature and supplied the changed files.
- Review: opened the integrated result and checked the critical path.
- Status: C1 verified; stakeholder approval is still required for C2.
「gpt-series-reasoning-style」を使用しています。 Confirm that this report is correct.
期待される結果:
The report matches the requested structure and its key figures were recalculated. Source freshness and business acceptance were not independently verified.
セキュリティ監査
安全All 91 static findings were adjudicated as false positives because they reference public metadata, documentation, fixed repository paths, or analysis heuristics rather than executed behavior. No prompt-injection text, data-exfiltration intent, or runtime command execution was evidenced in the reviewed files.
リスク要因
🌐 ネットワークアクセス (12)
📁 ファイルシステムへのアクセス (41)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/jadeyingwah-gpt-series-reasoning-style/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/jadeyingwah-gpt-series-reasoning-style?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/jadeyingwah-gpt-series-reasoning-style?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jadeyingwah-gpt-series-reasoning-style/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/jadeyingwah-gpt-series-reasoning-style.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形式の引用
jadeyingwah. (2026). gpt-series-reasoning-style security audit report (audit version 6) [Author version 1.6.0]. Skillstore. https://skillstore.io/skills/jadeyingwah-gpt-series-reasoning-style/audits/6BibTeX形式の引用
@techreport{jadeyingwah-jadeyingwah-gpt-series-reasoning-style-2026,
author = {jadeyingwah},
title = {gpt-series-reasoning-style security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/jadeyingwah-gpt-series-reasoning-style/audits/6},
note = {Author version 1.6.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gpt-series-reasoning-style security audit report (audit version 6)"
version: "1.6.0"
type: report
authors:
- name: "jadeyingwah"
date-released: "2026-09-20"
url: "https://skillstore.io/skills/jadeyingwah-gpt-series-reasoning-style/audits/6"
identifiers:
- type: other
value: "skillstore:jadeyingwah-gpt-series-reasoning-style:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Review a Code Change
Ask an engineer or coding agent to implement a change, run focused checks, open the result, and report verified and unverified paths.
Coordinate Multiple Agents
Use staged planning and explicit handoffs when several agents divide research, implementation, testing, or review.
Validate a Client Deliverable
Track whether a document, design, or analysis matches the request and distinguish technical completion from stakeholder approval.
これらのプロンプトを試す
Complete this task, then open the actual result and list what you verified, what remains unverified, and whether the request is complete.
Plan this task in clear stages. Identify the required checks and the real environment where the final result must be opened before you implement it.
Review this completed change against the original request. Recalculate important numbers, open the output, test the critical path, and mark every unverified claim.
Break this project into independent agent roles. Define handoff evidence, assign a reviewer, verify the integrated result in its real environment, and report the appropriate C1 or C2 status.
ベストプラクティス
- Define the evidence required for completion before implementation begins.
- Open and use the delivered result in the environment that matters.
- State verified facts, unverified paths, and completion level separately.
回避
- Do not declare completion from code inspection alone.
- Do not treat a green check as proof that the guarded failure case works.
- Do not label a result C2 without user or external confirmation.