353 件 ・ 関連度順
概要と使いどころ
Provides reverse engineering techniques for CTF challenges. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malwar
日本語の概要は準備中です。原文の説明を表示しています。
Provides cryptography attack techniques for CTF challenges. Use when attacking encryption, hashing, signatures, ZKP, PRNG, or mathematical crypto problems involving RSA, AES, ECC, lattices, LWE, CVP, number theory, Coppersmith, Pollard, Wiener, padding oracle, GCM, key derivation
日本語の概要は準備中です。原文の説明を表示しています。
Aşamalı CTF ipucu sistemi — takılan kullanıcıya seviyeli ipucu verir. Level 1 (nudge), Level 2 (direction), Level 3 (solution). Her challenge için hint seviyesi ~/.fetih/ctf_hints.json'da takip edilir.
日本語の概要は準備中です。原文の説明を表示しています。
CTF challenge ana orkestratörü — kategori tespiti, modern saldırı patern tanıma, ilgili skill arama, cross-skill zincir koordinasyonu, hızlı referans erişim. Auto-solver ve hint-system routing.
日本語の概要は準備中です。原文の説明を表示しています。
CTF challenge otomatik cozum pipeline'i. 6 asama: zip'i ac, siniflandir, coz, flag topla, writeup olustur. /auto-solve komutuyla cagrilir.
日本語の概要は準備中です。原文の説明を表示しています。
Finish an existing Japanese creator, challenge, comeback, vlog, or community-building vertical social rough cut as an evidence-grounded short-form story. Use for strong opening declarations, identity and struggle arcs, crisis-to-goal recovery, multi-source B-roll and evidence stills, emotional typography, semantic punch-ins, pinned SFX, dialogue-first audio, platform-added music delivery, and creator-short retention QA.
日本語の概要は準備中です。原文の説明を表示しています。
Installs the CARLA Autonomous Driving Leaderboard (leaderboard.carla.org) at a chosen version — 1.0, 2.0 or 2.1 — together with the exact scenario_runner branch and CARLA build each one requires, then wires the four-root PYTHONPATH and verifies the whole stack imports. Detects which version an existing checkout is by reading its code, not its branch name. Use when the user asks to "install the leaderboard", "set up the CARLA challenge", "evaluate my driving agent", "reproduce my leaderboard score", or names a leaderboard version.
日本語の概要は準備中です。原文の説明を表示しています。
Interact with challenge widgets in an authorized automation flow using checkbox clicks, slider drags, text OCR, and image-grid input. Verify completion with an application-specific condition.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial thesis testing — act as a short seller to find the weakest points in a thesis. Use when user says "stress test", "devil's advocate", "challenge this thesis", or "break [TICKER]".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model and sharpens terminology. Use when user wants to stress-test a plan against their project's language and documented decisions; propose documentation updates for approval as decisions crystallise.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate one or more thinking frameworks to work through any problem, decision, document, or idea rigorously. Diagnoses which frameworks fit — inversion, pre-mortem, assumption-mapping, socratic, adversarial-hat — then guides the user through them in the right sequence. Load when the user asks for deep thinking, says "help me think through this properly", "apply your best thinking frameworks", "I need to think carefully before deciding", or "what thinking tools should I use here". Also the entry point for any complex problem where the right framework is unclear. Covers product decisions, engineering tradeoffs, personal decisions, strategy, creative challenges — any domain.
日本語の概要は準備中です。原文の説明を表示しています。
Strip a problem to its irreducible fundamental truths and rebuild the solution from the ground up — free from analogy, convention, and inherited assumptions. Load when the user feels constrained by how something has always been done, when existing solutions feel expensive or inefficient for no good reason, when the user asks to think from first principles, challenge the fundamentals, or rebuild this from scratch. Also triggers on "why does it have to work this way", "what are the actual constraints here", "ignore what everyone else does", or when deep-thinking diagnoses a convention-break frame. Based on Aristotle's first principles method, popularised by Musk and Feynman. Produces genuinely novel solutions by eliminating convention.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about team driving — two-driver OTR operations, how teams maximize miles, HOS rules with sleeper berth swap, pay structures, equipment requirements (sleeper berth specs), team retention, and common challenges. Reference 49 CFR 395.1(g).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about refrigerated (reefer) trucking — cold chain compliance, FDA temperature recording requirements, Sanitary Transportation Rule (STR / 21 CFR 1.900-1.934), commodity-specific temperature ranges, refrigeration unit operation, temperature recorder calibration, and how a load is challenged if temperature deviates. Cite 21 CFR Part 1 Subpart Q.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to set proper expectations on how a DataQ challenge is actually reviewed. Covers state vs federal authority, typical timelines, and common review outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to evaluate which DataQ challenges have winning evidence and which don't. Covers documented vs anecdotal evidence and the 8 high-success patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when a crash has been incorrectly classified as DOT-recordable when it shouldn't be. Covers the § 390.5 criteria, common misclassifications, and challenge process.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when an inspection report identifies the wrong driver. Covers how to file a DataQ challenge for driver ID errors, evidence requirements, and reversal rates.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
日本語の概要は準備中です。原文の説明を表示しています。