Unclear requirements can lead AI assistants to make consequential choices without user agreement. This skill guides focused questions, bounded inspection, and review before material changes.
Review the Skillstore skill "ask-dont-assume" from https://skillstore.io/skills/shreyam1008-ask-dont-assume.md and its manifest at https://skillstore.io/api/skills/shreyam1008-ask-dont-assume/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
Static analysis reported no findings, so no per-finding verdicts were required. The reviewed skill defines clarification, bounded inspection, and review checkpoints without executable code. No evidence found of prompt injection, data exfiltration intent, or unauthorized external actions.
shreyam1008. (2026). ask-dont-assume security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-ask-dont-assume/audits/1
BibTeX形式の引用
@techreport{shreyam1008-shreyam1008-ask-dont-assume-2026,
author = {shreyam1008},
title = {ask-dont-assume security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/shreyam1008-ask-dont-assume/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: "ask-dont-assume security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "shreyam1008"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/shreyam1008-ask-dont-assume/audits/1"
identifiers:
- type: other
value: "skillstore:shreyam1008-ask-dont-assume:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由証拠の信頼度: 中
55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
91
仕様準拠
作成できるもの
Confirm Implementation Scope
Clarify platform, framework, and dependency choices before implementing a feature with multiple plausible approaches.
Resolve Product Tradeoffs
Separate agreed requirements from assumptions and ask focused questions about behavior, privacy, and cost before committing to a direction.
Confirm External Change Targets
Resolve ambiguous environments and destinations before publishing or writing externally, then review side effects and rollback expectations.
これらのプロンプトを試す
Clarify a Simple Request
Use ask-dont-assume for this task: [task]. Ask a focused question if an unresolved choice materially changes the result.
Preserve Agreed Requirements
Implement [feature] within [agreed scope]. Keep [settled decisions] fixed. Clarify consequential unknowns, but choose routine reversible details yourself.
Inspect Before External Changes
Prepare [change] for [possible environments]. Use safe read-only inspection to clarify ambiguity without exposing sensitive data. Do not mutate until consequential choices are resolved.
Handle Delegated Decisions
Choose an approach for [task] within [boundaries]. State the choice, evidence, and default before consequential changes. Review assumptions, side effects, verification, and rollback before handoff.
ベストプラクティス
State settled decisions and permission boundaries before starting the task.
Answer focused questions with the intended target, scope, and relevant tradeoffs.
Delegate routine choices explicitly and confirm consequential assumptions before material handoffs or external writes.
回避
Treating unclear permissions or deployment targets as approval to proceed.
Requesting confirmation for every formatting choice or helper name.
Reopening settled decisions without new evidence.
よくある質問
When should this skill ask a question?
When an unresolved choice materially affects behavior, scope, platform, dependencies, data, permissions, cost, privacy, or external state.
Will it interrupt routine implementation work?
It directs the assistant to choose routine, reversible details when they do not change scope or conflict with settled conventions.
Can the assistant inspect files while waiting?
Safe read-only inspection is allowed when it tests the ambiguity without committing to a choice or exposing sensitive data. Mutation must wait.
What happens when I delegate a decision?
The assistant should state the chosen default and supporting evidence before consequential changes, then document the choice and boundaries in the handoff.
What does the review checkpoint cover?
It covers facts, user decisions, remaining assumptions, scope, side effects, verification, rollback, and the next user-visible step before material handoffs or external writes.
Does this skill enforce access controls?
No. It guides assistant behavior but does not implement permission checks, sandboxing, or tool restrictions.