582 件 ・ 関連度順
概要と使いどころ
Use when an authorized reference surface needs a clean-room frontend reconstruction across static, motion, and responsive fidelity. Not for styling or component work without a reference surface.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect one bounded Proto UI pull-request slice, produce canonical review input, and route each eligible exact head toward review and integration. Use for review queues, linked work, evidence gaps, merge conflicts, stale revisions, or portfolio health. This evidence leaf is read-only; authorized review and integration continue in their registered leaves.
日本語の概要は準備中です。原文の説明を表示しています。
Record one authorized non-remediation terminal outcome in Proto UI's autonomous-maintenance state. Use after a supported no-finding result, an independently rejected finding, or a blocked mission whose terminal evidence is complete.
日本語の概要は準備中です。原文の説明を表示しています。
Audit one bounded Proto UI collaboration-governance slice and route policy-determined drift toward reversible correction. Use across Issues, pull requests, Discussions, labels, milestones, Project, rules, permissions, or Actions. This evidence leaf is read-only; authorized corrections continue in their registered leaves.
日本語の概要は準備中です。原文の説明を表示しています。
Release one current Proto UI work-item claim when it expired, became invalid, or the contributor stopped. Use only for the contributor's own recorded claim and only when the exact reversible GitHub mutation is authorized. Do not select replacement work, change readiness, or release another contributor's claim.
日本語の概要は準備中です。原文の説明を表示しています。
Publish one prepared Agent evidence packet as an additive Issue comment, including historical or closed Issues, under exact current authorization. Use after read-only Issue inspection and separately authorized evidence preparation. Do not reproduce, select work, upload assets, edit human text, claim, review, close, or change Issue metadata.
日本語の概要は準備中です。原文の説明を表示しています。
Post one already selected Proto UI work-item claim as a reversible GitHub metadata mutation. Use after pui-select produced a current proposal and the exact claim has authorization, live permission, current readiness, and an idempotent write boundary. Do not select work, decide readiness, release claims, or widen the authorized wording.
日本語の概要は準備中です。原文の説明を表示しています。
Run an authorized task inside an Available Work Time (AWT) window with a shorter Closeout Grace Period (CGP), fixed deadlines, forecast checks, proportional convergence points, and a hard stop. Use when the user explicitly requests timeboxing, supplies an AWT/CGP pair, says AWT or CGP, or an applicable project policy requires the protocol. Do not invent durations or activate timeboxing merely because a task may take time.
日本語の概要は準備中です。原文の説明を表示しています。
Use when user asks to setup endorctl, install endorctl, run endorctl scan, scan for vulnerabilities, run endor scan or run Endor Labs scan or when any endorctl command fails with 'command not found', 'no such file or directory', authentication errors, 'unauthorized', '403', 'tenant not found', EOF error, or namespace/access errors.
日本語の概要は準備中です。原文の説明を表示しています。
Run or continue an operator-authorized external ACP worker through cwr-acp when ACP is the operator's standing default or explicit task selection. Use the configured default or selected route with explicit per-turn permissions; mere native tool availability does not change the channel.
日本語の概要は準備中です。原文の説明を表示しています。
Choose the authorized worker channel and hand over complete engineering responsibilities, including in-scope self-check, repair and delivery. Use for substantial investigation, implementation, continuation and recovery; use swarm for approved independent batches. Respect the operator's standing ACP/native choice, explicit solo, and tiny or nearly finished work.
日本語の概要は準備中です。原文の説明を表示しています。
Identifying and validating cross-site scripting vulnerabilities using Burp Suite's scanner, intruder, and repeater tools during authorized security assessments.
日本語の概要は準備中です。原文の説明を表示しています。
Executes authorized attack simulations against Active Directory environments to identify misconfigurations, weak credentials, dangerous privilege paths, and exploitable trust relationships that could lead to domain compromise. The tester uses BloodHound for attack path analysis, Mimikatz for credential extraction, and Impacket for protocol-level attacks including Kerberoasting, AS-REP Roasting, and delegation abuse. Activates for requests involving Active Directory pentest, AD attack simulation, domain compromise testing, or Kerberos attack assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when exploring, continuing, or accepting a deep-learning or computer-science research idea. Converts claims into pilot-first experiment matrices covering diagnostics, failure analysis, authorized execution, evaluation, and paper-story viability.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, build, scaffold, or safely extend Atlassian Forge apps using current official documentation. Use for fresh Forge apps, existing-app feature work, module and manifest changes, UI Kit or Custom UI implementation, backend functions and events, Atlassian or external APIs, storage, permissions, environment configuration, distribution-affecting implementation, validation, and explicitly authorized deployment or installation; route standalone debugging and specialist reviews to their dedicated skills.
日本語の概要は準備中です。原文の説明を表示しています。
Smart contract and Web3 security audit skill for Solidity, Vyper, Move, and Cairo. Covers reentrancy, access control, oracle manipulation, MEV/sandwich exposure, signature replay, upgrade safety, ERC token edge cases, bridge risk, and DeFi invariants. Tooling includes Slither, Mythril, Echidna, Foundry, Halmo, Certora, and custom invariant tests. Use for design review, code audit, and incident analysis on contracts you own or are authorized to assess.
日本語の概要は準備中です。原文の説明を表示しています。
OSINT and reconnaissance automation skill for passive collection, pivoting, deduplication, and graph-based analysis using subfinder, amass, dnsx, chaos, crt.sh, github-dorks, waybackurls, gau, gitleaks, trufflehog, theHarvester, h8mail, holehe, sherlock, Shodan, Censys, FOFA, and Hunter. Use for asset discovery, exposure monitoring, and authorized reconnaissance only.
日本語の概要は準備中です。原文の説明を表示しています。
AI and LLM red-teaming skill for evaluating prompt injection, jailbreak, data exfiltration, tool abuse, agent hijack, RAG poisoning, model denial of service, and unsafe tool-use chains in Gemini, Claude, GPT, and open-weight models. Use to build evaluation harnesses, attack corpora, defensive guardrails, and red-team reports for AI systems you own or are authorized to test.
日本語の概要は準備中です。原文の説明を表示しています。
Top username lists for enumeration: common usernames, default credentials, names. Curated essentials for authorized testing.
日本語の概要は準備中です。原文の説明を表示しています。
Top password lists for authorized security testing: common passwords, darkweb leaks, worst passwords. Curated essentials (<10MB).
日本語の概要は準備中です。原文の説明を表示しています。
Exploit Mass Assignment vulnerabilities in APIs and web frameworks to inject unauthorized parameters. This skill details how attackers uncover hidden fields and manipulate JSON or HTTP bodies to elevate privileges or tamper with data logic.
日本語の概要は準備中です。原文の説明を表示しています。
Perform forensic analysis of the macOS Unified Logging System (ULS) to investigate system events, application crashes, kernel panics, and potential indicators of compromise (IoCs) such as persistence mechanisms or unauthorized access.
日本語の概要は準備中です。原文の説明を表示しています。