📦
w-docs
77Document Code Changes Clearly
Documentation updates often land in the wrong file or duplicate existing information. This skill directs the assistant to the owning documentation layer and keeps project guidance consistent.
ドキュメント 表示
スキル w-retro
📦
w-retro
コンテンツリビジョン r1 安全
Review Completed Work and Improve Next Time
Teams often finish tasks without recording what changed, what evidence was missing, or what should improve. This skill produces a concise, task-specific retrospective with up to three practical next steps.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "w-retro" from https://skillstore.io/skills/blockmatic-w-retro.md and its manifest at https://skillstore.io/api/skills/blockmatic-w-retro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「w-retro」を使用しています。 We needed to add export filtering. The filter shipped and unit tests passed, but no browser test was run.
期待される結果:
Requested versus shipped: Export filtering was added and unit-tested. Evidence gap: Browser behavior was not checked. Next change: Add one browser test for filter selection and downloaded results.
「w-retro」を使用しています。 The task was to update the onboarding guide. The guide changed, but the examples were not checked against the current interface.
期待される結果:
- Requested versus shipped: The onboarding guide was updated, but example accuracy was not verified.
- Process gap: The task lacked a user-interface consistency check.
- Next changes: Review examples against the current interface and add a lightweight documentation checklist.
セキュリティ監査
安全v1 • 2026/9/20 バージョン別レポートを開く
The scanned skill is a 12-line, chat-only retrospective checklist with no executable code or detected security patterns. No prompt-injection, data-exfiltration, or business-logic abuse evidence was found in SKILL.md.
1
スキャンされたファイル
12
解析済み行数
0
レビュー項目
0
誤検知を無視
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/blockmatic-w-retro/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/blockmatic-w-retro?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/blockmatic-w-retro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/blockmatic-w-retro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/blockmatic-w-retro.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形式の引用
blockmatic. (2026). w-retro security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/blockmatic-w-retro/audits/1BibTeX形式の引用
@techreport{blockmatic-blockmatic-w-retro-2026,
author = {blockmatic},
title = {w-retro security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/blockmatic-w-retro/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: "w-retro security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "blockmatic"
date-released: "2026-09-20"
url: "https://skillstore.io/skills/blockmatic-w-retro/audits/1"
identifiers:
- type: other
value: "skillstore:blockmatic-w-retro:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
91
仕様準拠
作成できるもの
Close a development task
Review the request, shipped changes, checks, and documentation before closing a coding task.
Improve team delivery
Capture specific process gaps after a sprint item, project milestone, or cross-functional deliverable.
Evaluate an AI-assisted workflow
Compare the requested work with the AI-produced result and record better checks for the next session.
これらのプロンプトを試す
Basic task retrospective
Review the completed task in this conversation. State what was requested, what shipped, and one improvement for next time.
Check process gaps
Run a retrospective on this completed task. Identify skipped checks, unclear requirements, extra scope, and missing documentation. Suggest no more than three specific changes.
Compare plan and outcome
Compare the original request, plan, implementation, and validation evidence. Explain the most important differences and recommend up to three changes for the next similar task.
Audit an AI-assisted delivery
Perform a task-specific retrospective of this AI-assisted delivery. Separate outcome gaps from process gaps, cite the available evidence, and prioritize three changes that would improve the next session.
ベストプラクティス
- Run the skill after checks are complete and the delivered result is known.
- Provide the original request, completed work, validation evidence, and relevant constraints.
- Prefer specific recommendations tied to this task over broad process advice.
回避
- Do not use the retrospective as a substitute for implementing a required fix.
- Do not request generic lessons without sharing task-specific evidence.
- Do not turn a short retrospective into an unfocused list of every possible improvement.
よくある質問
When should I use this skill?
Use it after completing a task and recording the checks or evidence that support the result.
What does the skill review?
It compares the request with the shipped result and checks for process or evidence gaps.
How many improvements does it suggest?
It suggests at most three concrete changes for the next similar task.
Can it change files or create commits?
No. It responds in chat and does not implement changes, commit files, or open pull requests.
What context produces the best result?
Include the request, plan, completed work, validation checks, constraints, and known uncertainties.
Does it replace a formal incident review?
No. It supports routine task learning and does not replace incident, compliance, or security review processes.
開発者情報
作成者
blockmaticライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
7cd60e5c44d39477abb7a2c00ae0de2cf2a01392
メンテナンスの新しさ
2026/9/20
利用状況
0 ダウンロード · 0 閲覧
ファイル構成
📄 SKILL.md
blockmatic のその他のスキル
すべて表示📦
w-diagram
77Map Code and Architecture with Mermaid
Complex code and documentation can be difficult to understand quickly. This skill turns inspected relationships, flows, and structures into focused Mermaid diagrams.
コーディング＆開発 表示
📦
w-api-docs
77Refresh API Docs from Source Schemas
API documentation can drift from the schemas and routes that define actual behavior. This skill guides updates from the owning source and keeps generated artifacts out of manual edits.
ドキュメント 表示
📦
w-release
77Review Release Impact Before You Ship
Release changes can miss affected packages, generated templates, tests, or required adopter actions. This skill structures a focused review of release impact, changelog updates, classification, and human approval gates.
DevOps＆インフラ 表示
📦
w-lint
77Run and Fix Project Lint Errors
Lint issues can slow development and leave code quality problems unresolved. This skill runs the project lint workflow, applies small fixes, and checks the result again.
コーディング＆開発 表示
📦
w-council
77Explore Codebases With Parallel Agents
Codebase investigations can miss important context when one review follows a single path. This skill coordinates focused explorers, reconciles their evidence, and produces a clear handoff.
調査＆学習 表示
関連スキル
すべて表示📦
sprint-retrospective
79より良いスプリントレトロスペクティブを実施する
作成者 supercent-io
スプリントチームには、課題を実践的な改善へ変えるための構造化された振り返りが必要です。このスキルは、Claude、Codex、またはClaude Codeに、レトロスペクティブの形式、アクションアイテム、フォローアップの実践を案内します。
生産性 表示
📦
task-state-ledger
90Track Long Tasks With a Portable State Ledger
作成者 glenskii
Long technical tasks lose decisions, evidence, and next actions across sessions. This skill maintains a concise Markdown state file with reviewed local evidence references.
生産性 表示
📦
gpt-series-reasoning-style
90Verify AI Deliverables with Evidence
作成者 jadeyingwah
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.
生産性 表示
📦
tool-discovery
87あらゆるタスクに適したAIツールを選択
作成者 0xDarkMatter
多数のスキルやエージェントから選択することで、技術作業が遅れる場合があります。このスキルは、簡潔なカタログと選択ルールを使用して、各タスクを目的に特化したツールに割り当てます。
生産性 表示
📦
dbs-human-dispatch
87Delegate Tasks and Verify Team Deliverables
作成者 dontbesilent2025
Unclear assignments and scattered feedback make team delivery difficult to verify. This skill creates task briefs, coordinates authorized follow-up, and checks deliverables against agreed criteria.
生産性 表示
📦
prompt-engineering-patterns
86本番環境向けLLMプロンプトを最適化
作成者 wshobson
LLMプロンプトは、指示、例、評価基準が不明確なために失敗することがよくあります。このスキルは、Claude、Codex、Claude Code、および同様のツールでプロンプトを改善するためのテンプレートとワークフローを提供します。
生産性 表示