descriptive-action
Analyze Information Neutrally
Users often need neutral analysis without recommendations. This skill guides Claude, Codex, and Claude Code to separate facts, inferences, evidence, and unknowns.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "descriptive-action" from https://skillstore.io/skills/bellabe-descriptive-action.md and its manifest at https://skillstore.io/api/skills/bellabe-descriptive-action/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "descriptive-action". A user provides meeting notes about delayed onboarding and asks for a neutral summary.
Expected outcome:
The response lists the main delay themes, separates confirmed points from inferred causes, cites note excerpts, and names unresolved questions.
Using "descriptive-action". A team provides two product feedback summaries and asks for a comparison.
Expected outcome:
The response describes shared themes, distinct complaints, evidence strength, and gaps without recommending roadmap changes.
Using "descriptive-action". An engineer provides logs and observations from a service incident.
Expected outcome:
The response summarizes observed behavior, likely relationships, supporting evidence, constraints, and unknowns for follow-up analysis.
Security Audit
SafeThe only static finding is a false positive. The cited line instructs the model to avoid normative language, which supports neutral analysis and does not request reconnaissance or sensitive system discovery.
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bellabe-descriptive-action/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bellabe-descriptive-action?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bellabe-descriptive-action?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bellabe-descriptive-action/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bellabe-descriptive-action.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
BellaBe. (2026). descriptive-action security audit report (audit version 8) [Author version 1]. Skillstore. https://skillstore.io/skills/bellabe-descriptive-action/audits/8BibTeX citation
@techreport{bellabe-bellabe-descriptive-action-2026,
author = {BellaBe},
title = {descriptive-action security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/bellabe-descriptive-action/audits/8},
note = {Author version 1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "descriptive-action security audit report (audit version 8)"
version: "1"
type: report
authors:
- name: "BellaBe"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/bellabe-descriptive-action/audits/8"
identifiers:
- type: other
value: "skillstore:bellabe-descriptive-action:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Summarize Research Notes
Turn long notes into neutral summaries with evidence and open questions.
Compare Product Feedback
Describe themes, differences, and constraints across user feedback without proposing product changes.
Explain System Behavior
Describe observed system behavior, relevant evidence, and unknowns for review.
Try These Prompts
Summarize the following material neutrally. Separate facts, inferences, evidence, and open questions.
Explain this material for [audience]. Use sections for summary, details, evidence, and open questions. Avoid recommendations.
Compare these items using only the provided information. Describe similarities, differences, evidence, and uncertainty.
Analyze the provided system observations. Identify supported findings, possible interpretations, evidence, constraints, and missing information.
Best Practices
- Provide the source material, audience, timeframe, and scope before asking for analysis.
- Ask for facts, inferences, evidence, and open questions when accuracy matters.
- Request a comparison table or short sections when reviewing multiple inputs.
Avoid
- Do not use this skill when you need recommendations, strategy, or action steps.
- Do not ask it to infer facts that are not supported by the provided material.
- Do not omit important constraints such as audience, timeframe, or source quality.