Autonomous pentest campaign driver. Runs a scoped engagement end to end with no operator approvals - the deterministic driver (scripts/campaign.py) owns pass state, generates the killchain board from recon, and prints the exact next action (Skill + tool) every turn. Use when starting or resuming a pentest, "run the pt workflow", "work this CIDR/domain", or when handed a client SoW/scope to reach a stated objective or domain admin. Single agent, refuter-verified, wiki-first, tool-first. Deliverable is a client report.
日本語の概要は準備中です。原文の説明を表示しています。
Encod3d-Sec/TORCH☆ 3332026年9月1日 更新
Autonomous CTF / boot-to-root campaign driver. Runs a box end to end with no operator approvals - the deterministic driver (scripts/campaign.py) owns pass state, generates the killchain board from recon, and prints the exact next action (Skill + tool) every turn. Use when handed a box/IP to own end to end, "run the ctf workflow", "root this box", "foothold to root". Single agent, wiki-first, tool-first. OSINT is OFF unless you invoke with an osint argument. Delegates box recipes to ctf-box.
日本語の概要は準備中です。原文の説明を表示しています。
Encod3d-Sec/TORCH☆ 3332026年9月1日 更新
Autonomous bug-bounty campaign driver. Runs a full programme end to end with no operator approvals - the deterministic driver (scripts/campaign.py) owns pass state, generates the killchain board from recon, and prints the exact next action (including which Skill and tool to run) every turn. Use when starting or resuming a bug-bounty engagement, "run the bb workflow", "hunt this program", "9-pass campaign", or when handed a *.scope wildcard to test for TIER1 findings. Single agent, refuter-verified, wiki-first, tool-first.
日本語の概要は準備中です。原文の説明を表示しています。
Encod3d-Sec/TORCH☆ 3332026年9月1日 更新
Synthesize raw recon/test output into engagement state. Reads everything dropped in targets/<active>/ingest/, extracts hosts/assets/creds/paths, merges into state.md/loot.md/Killchain.md, logs it, archives the raw files. Works for pentest, bugbounty, and ctf. Use when asked to "ingest", "synthesize findings", "process recon", or after dropping tool output in the ingest folder.
日本語の概要は準備中です。原文の説明を表示しています。
Encod3d-Sec/TORCH☆ 3332026年9月1日 更新
Harvest every `honey:` comment in the codebase into a debt ledger, so the deliberate shortcuts Lever 1 leaves behind get tracked instead of rotting into "later means never". Flags markers with no revisit trigger — those are the ones that go permanent silently. Use when the user says "honey debt", "/honey-debt", "what did honey defer", "list the shortcuts", or "what did we mark to do later". One-shot report; changes nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Green-PT/honey-for-devs☆ 3322026年9月7日 更新
Rewrite a memory or context file (CLAUDE.md, AGENTS.md, a todo or notes file) into Honey-terse form so it costs fewer input tokens every session, without losing meaning. Backs up the original first. Use when asked to shrink or compress context files, trim CLAUDE.md, or cut per-session input cost. Prose only — never code, config, or data.
日本語の概要は準備中です。原文の説明を表示しています。
Green-PT/honey-for-devs☆ 3322026年9月7日 更新
Write less code and say less about it: YAGNI, stdlib-first, terse prose. Cuts agent token cost on every coding and writing task.
日本語の概要は準備中です。原文の説明を表示しています。
Green-PT/honey-for-devs☆ 3322026年9月7日 更新
Honey for plain Claude — the terse-prose core with no agent-harness features. Paste into a claude.ai Project's custom instructions, a Style, or an API system prompt. Strips filler, hedging, and pleasantries from every response while keeping facts, names, numbers, steps, and code exact. No tools required.
日本語の概要は準備中です。原文の説明を表示しています。
Green-PT/honey-for-devs☆ 3322026年9月7日 更新
Create and maintain one committed per-project memory file (PROJECT.md) so agents stop re-discovering the same facts every cold session. Stores only the stable, expensive-to-rediscover, not-in-the-code context — architecture + why, build/test/run commands, decisions and dead-ends — as human-readable markdown, versioned with the code so it can't silently rot. Use when asked to set up project memory/context, stop agents re-grepping the codebase, scaffold or refresh a PROJECT.md / CLAUDE.md memory section, or cut cold-start rediscovery cost. Prose context only — never code, config, or data.
日本語の概要は準備中です。原文の説明を表示しています。
Green-PT/honey-for-devs☆ 3322026年9月7日 更新
Harvest every `honey:` shortcut marker into a debt ledger, flagging the ones with no revisit trigger. One-shot report, changes nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Green-PT/honey-for-devs☆ 3322026年9月7日 更新
Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using the product creates no new users.
日本語の概要は準備中です。原文の説明を表示しています。
AIDevGTM/gtm-cofounder☆ 3182026年10月15日 更新
Position an AI product when everyone claims AI and skeptics call it "just a wrapper." Find the real wedge (data, workflow, trust, domain), make reliability the differentiator, answer "won't the big labs just build this," and stop leading with "AI-powered." Use when your AI or dev tool blends into a sea of similar demos, buyers doubt the accuracy, or you can't say why you win when the model is a commodity.
日本語の概要は準備中です。原文の説明を表示しています。
AIDevGTM/gtm-cofounder☆ 3182026年10月15日 更新
Interview the user once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a textbook. Use this before anything else, or whenever the agent lacks context on the user's product, ICP, market, or stage, or is giving generic GTM advice.
日本語の概要は準備中です。原文の説明を表示しています。
AIDevGTM/gtm-cofounder☆ 3182026年10月15日 更新
After the founder brief, turn it into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the hub the user returns to every session to see where they are and the single next move. Use right after start-here, whenever the user doesn't know what to work on next, wants a plan instead of a one-off task, or is drowning in disconnected tactics.
日本語の概要は準備中です。原文の説明を表示しています。
AIDevGTM/gtm-cofounder☆ 3182026年10月15日 更新
Build a positioning and narrative where the developer is the hero and a real trend is the villain. Use when the messaging describes the product instead of the problem, sounds like every competitor, or has no urgency because nothing is at stake.
日本語の概要は準備中です。原文の説明を表示しています。
AIDevGTM/gtm-cofounder☆ 3182026年10月15日 更新
This skill should be used when the user asks to "create a style sheet", "style guide", "house style", "keep the voice consistent", "voice drift", "British or American spelling", "character voices", "lint the prose", "prose check", "filter words", "said-bookisms", "overused words", "repeated phrases", "similar character names", "voice fingerprints", or wants to record and enforce the voice and surface conventions of a story project. NOT for rewriting dialogue to make the voices distinct when everyone sounds the same (use line-editing), or a character's profile or arc (use character-management).
日本語の概要は準備中です。原文の説明を表示しています。
danjdewhurst/story-skills☆ 3112026年10月15日 更新
This skill should be used when the user asks to "line edit", "edit my prose", "polish this chapter", "tighten the prose", "improve the sentences", "copyedit", "proofread", "proof pass", "check grammar and punctuation", "dialogue punctuation", "make the voices distinct", "everyone sounds the same", "read it aloud", "read-aloud pass", "text to speech", or wants a sentence-level quality pass on drafted chapters that preserves the author's voice. NOT for creating the style sheet, recording character voices, or checking voice consistency (use voice-style).
日本語の概要は準備中です。原文の説明を表示しています。
danjdewhurst/story-skills☆ 3112026年10月15日 更新
Everyday and hero prop modeling for furniture, tools, household objects, kitbash parts, and readable game props. Use when hard-surface is too sci-fi/mechanical and the asset is a grounded prop.
日本語の概要は準備中です。原文の説明を表示しています。
arjun988/blender-skills☆ 3102026年7月11日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
lingxling/awesome-skills-cn☆ 3092026年10月7日 更新
Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points.
日本語の概要は準備中です。原文の説明を表示しています。
lingxling/awesome-skills-cn☆ 3092026年10月7日 更新
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
日本語の概要は準備中です。原文の説明を表示しています。
lingxling/awesome-skills-cn☆ 3092026年10月7日 更新
Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.
日本語の概要は準備中です。原文の説明を表示しています。
lingxling/awesome-skills-cn☆ 3092026年10月7日 更新
Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them.
日本語の概要は準備中です。原文の説明を表示しています。
lingxling/awesome-skills-cn☆ 3092026年10月7日 更新
Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wants to be walked through, taught, paced through, or shown around code or a branch step by step, or to learn how a change works before reviewing or extending it. Stops after every step and waits, so the learner sets the pace. Paces through code that already exists and builds nothing — to build new work while being paced through it, use pairing. Does not produce a written overview to read alone — use code-overview. Does not review code quality — use code-review. Does not diagnose bugs — use investigate.
日本語の概要は準備中です。原文の説明を表示しています。
testdouble/han☆ 3032026年10月15日 更新