1,644 件 ・ 関連度順
概要と使いどころ
Android pentesting playbook. Use when testing Android applications for SSL pinning bypass, exported component abuse, WebView vulnerabilities, intent redirection, root detection bypass, tapjacking, and backup extraction during authorized mobile security assessments.
日本語の概要は準備中です。原文の説明を表示しています。
Active Directory security audit using the MITRE ATT&CK framework. Full domain enumeration, trust mapping, GPO analysis, ACL abuse paths, ADCS attacks (ESC1-ESC8), delegation abuse (constrained/unconstrained/RBCD), fine-grained password policies, LAPS deployment, service account security, and Kerberos configuration. Uses enum4linux-ng, netexec, impacket, ldapsearch, certipy-ad, bloodhound-python, and rpcclient. Produces attack path diagrams, prioritized risk register, and PoCs. Chains into /gh-export for issue filing.
日本語の概要は準備中です。原文の説明を表示しています。
Search a named company's careers board, or resolve a natural-language query into a company list and search each. Extract job descriptions, score pool-anchored and channel-conditional fit against the user's profile, run a contrarian gate before tiers are finalized, and create role folders with assessments. Updates the job search tracker.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user to surface experience that is real but undocumented, mapped against a specific role's requirements, then update the profile. Use when a fit assessment or an adversarial review flags a section as thin.
日本語の概要は準備中です。原文の説明を表示しています。
Frappe LMS customization guidance for courses, batches, lessons, quizzes, assessments, enrollment, progress, certificates, portals, and learning workflows. Use when work touches Frappe LMS or education/training flows.
日本語の概要は準備中です。原文の説明を表示しています。
In-house legal workflows for contract review against playbooks, NDA triage with GREEN/YELLOW/RED ratings, compliance briefings, and vendor checks. Use when the user invokes /review-contract, /triage-nda, /legal-risk-assessment, or /vendor-check for organisation-standard legal analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a direct five-axis code review across correctness, security, performance, readability, and maintainability. Use when the user asks for `/review`, PR review, security review, pre-merge review, production readiness review, or blocking issue assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user wants to turn code graph analysis into tracked GitHub issues — "audit the architecture", "find god nodes", "triage architectural debt", "run graphify and log issues", "what's over-coupled in this codebase", "create issues from graphify findings", "check for structural problems", "scan for architectural smells", or any request that combines codebase topology analysis with issue tracking. This skill runs graphify to build a dependency graph, parses GRAPH_REPORT.md for god nodes and structural patterns, converts findings into GitHub issue payloads, and optionally pushes them to the repo. It bridges static analysis and project management in a single automated pass. Requires graphify and gh CLI.
日本語の概要は準備中です。原文の説明を表示しています。
UI design and implementation for real product surfaces with taste-first critique, reference routing, project-specific design briefs, variation comparison, and implementation verification. Use when Codex should redesign, build, polish, or critique frontend UI by reading project context, exploring taste, routing through `references/catalog.md`, synthesizing `PROJECT_DESIGN.md` or `design.md`, using investment gates to avoid wrong taste/reference/scope, implementing in the existing stack, and evaluating whether the result is actually better. Best for app screens, dashboards, landing pages, query tools, product surfaces, and design explorations; not for backend-only work or tiny cosmetic edits.
日本語の概要は準備中です。原文の説明を表示しています。
This skill provides expert-level guidance for refactoring VS Code extension code. Use when extracting classes or functions, reducing code duplication, improving type safety, reorganizing module structure, applying design patterns, or optimizing performance. Covers systematic refactoring workflows, code smell detection, safe transformation techniques, and VS Code-specific patterns.
日本語の概要は準備中です。原文の説明を表示しています。
This skill provides systematic bug detection and discovery capabilities for VS Code extensions. Use when searching for hidden bugs, analyzing code for potential issues, investigating suspicious behavior, performing code audits, or proactively finding bugs before they manifest. Covers static analysis patterns, dynamic analysis techniques, code smell detection, and systematic codebase investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Performs fast first-pass triage of an unknown file to decide depth of analysis: file type identification, hashing, reputation lookup, packing/entropy check, and string review. Activates for requests to triage, classify, or do initial assessment of an unknown or suspicious file.
日本語の概要は準備中です。原文の説明を表示しています。
Deep code review - Elixir idioms, Phoenix patterns, architecture, safety. Launches 3 parallel reviewers + plan-reviewer gate. Use when: review, review this, code review, check this code, review my changes, is this good, what do you think, code smells.
日本語の概要は準備中です。原文の説明を表示しています。
Master orchestrator for B2B SaaS content creation and the editorial production system behind it. Use this skill to produce blog articles, whitepapers, case studies, video scripts, newsletters and ghostwritten thought leadership, to develop content strategy, and to run the publishing line itself — content briefs, editorial calendars and production capacity, review and approval workflow, subject-matter-expert access, the style guide, an AI-drafting policy, and a content inventory with owners. Also triggers on: blog, article, case study, whitepaper, newsletter, video script, ghostwriting, content calendar, editorial, thought leadership, content strategy, content brief, content operations, content ops, editorial workflow, managing editor, who reviews this, our content pipeline is stuck, content is stuck in review, content audit, content inventory, content governance, style guide, house style, SME interview, expert interview, freelance writers, AI content policy, how much content can we actually produce. Also owns the customer academy and customer education: online courses, onboarding curriculum, tutorials, certification programs, digital credentials and badges, exam and pass-mark design, course freshness when the product UI changes, and whether the academy should sit behind a login. Triggers on: customer academy, customer education, online course, course library, learning path, curriculum, tutorial, certification program, certified users, digital badge, Open Badges, recertification, exam, pass mark, LMS, Skilljar, our tutorial shows the old UI, our course is out of date, should the academy be gated, do certified customers renew better.
日本語の概要は準備中です。原文の説明を表示しています。
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
日本語の概要は準備中です。原文の説明を表示しています。
需要在不修改业务代码的前提下诊断既有前端代码的结构性可维护性问题，并要求提供证据、误判检查与候选重构方向时。
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for general frontend code review, PR review, merge-readiness assessment, architecture maintainability, type-safety, rendering/state risks, style consistency, testability gaps, or a cross-cutting review summary. Delegate deep security, accessibility, E2E, or performance investigations to their specialized skills; Chinese triggers include code review, code review, review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when diagnosing structural maintainability problems in existing frontend code before deciding how to refactor it, especially when evidence, false-positive checks, and candidate transformations are needed without editing business code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an environmental scientist — scoping or reviewing a Phase I/Phase II environmental site assessment, interpreting soil or groundwater sampling results against regulatory action levels, drafting an environmental impact statement or NEPA scoping document, running a contaminant fate-and-transport screening calc, or assessing ecological risk to a receptor.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Engineering Teacher, Postsecondary — diagnosing a spike in a gatekeeper course's D/F/W rate, running a capstone design course with an industry sponsor, closing the loop on an ABET student-outcome assessment, or building a tenure/promotion teaching-effectiveness case beyond raw student evaluation scores.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Elementary School Teacher — interpreting a running record or fluency check against grade-level benchmarks, deciding whether a struggling reader needs a Tier 2 intervention, running a self-contained classroom's daily schedule across multiple subjects, implementing (not writing) an IEP/504 accommodation with fidelity, or writing a parent-conference summary grounded in assessment data.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Postsecondary Computer Science Professor — diagnosing why a course's DFW (D/F/withdraw) rate spiked, redesigning an intro programming course's assessment structure, staffing TAs and grading load for a large course, deciding what to prioritize pre-tenure, running an academic-integrity (MOSS similarity) investigation, or mapping a curriculum change against ABET student outcomes.
日本語の概要は準備中です。原文の説明を表示しています。