1,146 件 ・ 関連度順
概要と使いどころ
Analyze Windows Shellbag registry artifacts to reconstruct folder browsing activity, detect access to removable media and network shares, and establish user interaction with directories even after deletion using SBECmd and ShellBags Explorer.
日本語の概要は準備中です。原文の説明を表示しています。
Enumerate Entra ID with ROADrecon and acquire and exchange tokens with roadtx.
日本語の概要は準備中です。原文の説明を表示しています。
Parse Windows PowerShell Script Block Logs (Event ID 4104) from EVTX files to detect obfuscated commands, encoded payloads, and living-off-the-land techniques. Uses python-evtx to extract and reconstruct multi-block scripts, applies entropy analysis and pattern matching for Base64-encoded commands, Invoke-Expression abuse, download cradles, and AMSI bypass attempts.
日本語の概要は準備中です。原文の説明を表示しています。
Leverages Splunk Enterprise Security and SPL (Search Processing Language) to investigate security incidents through log correlation, timeline reconstruction, and anomaly detection. Covers Windows event logs, firewall logs, proxy logs, and authentication data analysis. Activates for requests involving Splunk investigation, SPL queries, SIEM log analysis, security event correlation, or log-based incident investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Examine file system slack space, MFT entries, USN journal, and alternate data streams to recover hidden data and reconstruct file activity on NTFS volumes.
日本語の概要は準備中です。原文の説明を表示しています。
Parse Windows Prefetch files using the windowsprefetch Python library to reconstruct application execution history, detect renamed or masquerading binaries, and identify suspicious program execution patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
日本語の概要は準備中です。原文の説明を表示しています。
Uses the Linux Audit framework (auditd) with ausearch and aureport utilities to detect intrusion attempts, unauthorized access, privilege escalation, and suspicious system activity. Covers audit rule configuration, log querying, timeline reconstruction, and integration with SIEM platforms. Activates for requests involving auditd analysis, Linux audit log investigation, ausearch queries, aureport summaries, or host-based intrusion detection on Linux.
日本語の概要は準備中です。原文の説明を表示しています。
Pull remote changes and reconcile with local work, checking for soft conflicts
日本語の概要は準備中です。原文の説明を表示しています。
Draft public Tamanu release notes for a given version. Use when the user wants release notes for a Tamanu release (e.g. "draft release notes for v2.45"). Pulls work from the specs and code that landed in that version's release/X.Y branch, plus the matching issues in the trackers (Linear's Tamanu team and Workhorse's Tamanu workspace), reconciles them, and writes docs/release-notes/vX-YY.md in the canonical v2.44 format for project managers and system administrators, plus a styled HTML rendering at .workhorse/design/designs/vX-YY-release-notes.html. Not for developer changelogs or QA test scoping (use scope-tamanu-release-tests for the latter).
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate, introduce, or refactor persistence abstractions when direct Eloquent is insufficient. Use for repository requests, complex aggregate reconstruction, or multiple persistence implementations; reject CRUD wrappers without a concrete benefit.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a codebase as a read-only senior advisor, prioritize evidence-backed improvements, and write self-contained implementation plans. Use for codebase audits, improvement roadmaps, focused planning, plan review, plan reconciliation, or executing an existing improve plan through an isolated Codex worktree. The advisor never edits source code; execution uses codex-improve and returns to the main agent for review.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when creating UAT (User Acceptance Testing) test cases in Excel format for Salesforce CRM projects. It generates standardized test case documents with summary sheets and detailed test case lists, following a specific format structure with test case ID, priority, category, scenario, preconditions, test steps, expected results, and acceptance criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Advisory checkpoint for deciding whether planning-document edits should be split into a separate planning branch/PR. Use only when the user explicitly asks where to commit `memory/SPEC.md` or `memory/PLAN.md` changes, mentions planning-doc merge conflicts, asks for a planning PR, or instructs you to prepare/submit one. Do not trigger for ordinary ln-* planning edits, one-line status updates, or routine canonical reconciliation.
日本語の概要は準備中です。原文の説明を表示しています。
Signpost (not a knowledge pack) for OMG modelling specifications — UML, SysML, BPMN, UAF, SoaML, MOF, OCL, XMI, DDS. Contains NO source content: it only points to where the official specs live and what each is for. Use when you need an OMG modelling/architecture specification — the OMG licence forbids redistributing or transforming the text, so these cannot be reconstituted into a pack; download them from OMG directly.
日本語の概要は準備中です。原文の説明を表示しています。
Reads a risk register together with meeting notes and incident reports and returns a draft update pack: existing risks whose exposure, controls, ownership or status the sources say have changed, new risk candidates, closure candidates, and the one owner decision each item needs. Never assigns or changes a likelihood, impact, score or colour and never edits the register; owners decide. Use when the user asks to "update the risk register from these minutes", "refresh the register with the incidents since the last review", "reconcile the register against the notes" or "what changed on our risks". Do not use for writing up an incident itself, use incident-postmortem-drafter or data-incident-impact-brief instead; to track actions from minutes, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Turns an engineer's notes, a ticket history or a chat thread into a draft step-by-step runbook with preconditions, stop conditions, numbered steps with checks, verification, rollback and escalation, for the team to validate before use. Commands verbatim, placeholders marked, every gap UNKNOWN; never executes a step or fills a gap from general knowledge. Use when the user asks to "write a runbook from these notes", "turn this resolved ticket into a runbook", "document the steps we ran" or "check this runbook for gaps". Do not use for a business process without commands, use sop-drafter instead; for a knowledge article or known-error record, use knowledge-article-drafter; for the post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Sweeps the last 24 hours of email, chat messages and meeting transcripts for commitments in both directions, what the user promised others and what others promised the user, reconciles them against a running commitments ledger (open, done, overdue), lists overdue items first and returns the updated ledger plus a proposed task list as Markdown for the user to save. Use when the user asks to "check my commitments", "what did I promise", "what am I owed", "did anything slip" or "run the commitment sweep". Do not use for a general morning summary of mail, calendar and mentions, use custom-daily-brief instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a list of KPIs or metrics into a DRAFT definition sheet: one row per KPI with the name as stated, formula quoted from a source, source system, owner, refresh cadence, unit, filters and known caveats, with UNKNOWN in every cell no source fills and a gap list grouped by data owner. Never composes a formula, sets a target or names an owner the sources do not state. Use when the user asks to "define these KPIs", "build a metrics definition sheet", "document how each KPI is calculated", "which of our KPIs have no owner or formula" or "reconcile the two KPI lists". Do not use for the weekly numbers report, use kpi-weekly-report-writer instead; for field-level definitions of a table, use data-dictionary-builder; for logging a wrong figure as a defect, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Read and understand PDF documents with the pdf_* tools - inspect a document before reading it, extract text in reading order or as reconstructed layout, search a document without reading all of it, recognize scanned pages that have no text layer, and render pages as pictures. Covers scanned documents, chat attachments, page-range and character caps, and the read-only and untrusted-content rules.
日本語の概要は準備中です。原文の説明を表示しています。
Close a work session properly: reconcile it against the wider collaboration, inventory what was actually built from git log and recently-touched files, summarize the arc, classify each artifact as keep, one-off or promote-to-permanent, route the durable ones to memory, canon or a new skill, save the retro as a vault note, and hand back an enriched /compact block so working memory shrinks without losing the thread. Triggers: "/retro", "/rr", "wrap up the session".
日本語の概要は準備中です。原文の説明を表示しています。
Operating manual for Telegram over its MCP connector and roughly 115 tools: how to find a chat by title, the tool inventory grouped by job, resolving chat ids, auto-transcribing voice notes, and the connector gotchas (pinned-first ordering, big-page crashes, reload after reconnect, untrusted fields, always passing an explicit account). Load before any non-trivial Telegram work.
日本語の概要は準備中です。原文の説明を表示しています。
Reconstruct a daily or weekly worklog from observed activity and outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Authorized multi-stage attack-path planning and orchestration spanning reconnaissance, initial access, privilege escalation, lateral movement, and reporting. Entry point for full engagements and cross
日本語の概要は準備中です。原文の説明を表示しています。