yakit-basic

Explains Yakit architecture, interface modes, feature routes, and engine connection for new users.

10|1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/yaklang/yak-skills --skill yakit-basic-yaklang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yakit-basic
Source: https://github.com/yaklang/yak-skills/tree/main/skills/yakit-basic
Command: npx skills add https://github.com/yaklang/yak-skills --skill yakit-basic-yaklang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New Yakit users often struggle to understand what the tool is, how its Electron frontend relates to the yaklang engine, where each security testing feature lives in the UI, and how to connect the engine or switch projects. This Skill provides a single entry-point guide that answers "what is Yakit", "where is feature X", and "why won't the engine connect". ## Core Features & Use Cases - Architecture Overview: Explains the three-layer structure of Electron frontend, yaklang gRPC engine, and the profile/project dual-database model. - Feature Route Tables: Maps every core UI function (MITM, Web Fuzzer, Codec, port scanning, plugins, reverse connection, databases, AI features, code audit) to its route key and purpose. - Onboarding Path: Provides a step-by-step beginner workflow from engine connection through MITM capture, Web Fuzzer replay, Codec, and plugin installation. - Use Case: A user asks "Where do I find the port scanner in Yakit?" or "How do I switch projects without losing my plugins?" — the Skill routes them to the correct UI area and explains the underlying behavior. ## Quick Start Ask the AI to explain how Yakit's frontend and engine work together and where to find the MITM hijack feature in the interface.

Frequently Asked Questions about yakit-basic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get started with Yakit for security testing?▼

Start by launching Yakit and connecting a local or remote yaklang engine, then open MITM interactive hijacking to capture browser traffic. From there, send requests to Web Fuzzer for replay, use Codec for encoding, and install community plugins from the plugin hub.

What is the relationship between Yakit frontend and the yaklang engine?▼

Yakit's Electron frontend is a display and interaction layer that communicates with the local yaklang engine process over gRPC bidirectional streams. The engine executes all yak scripts, scanning, MITM proxying, and packet sending, while the frontend renders ExecResult streams as logs, tables, and charts.

Where is the port scanning feature in Yakit?▼

Port scanning with fingerprint identification is under the security tools group with route key scan-port. Other tools in the same group include PoC-based vulnerability detection, weak password brute forcing, and space engine search.

Does switching Yakit projects delete my installed plugins?▼

No. Switching projects only changes the project database containing History, Risks, ports, and domains. Plugins, Payload dictionaries, and global configuration live in the profile database, which is shared across all projects.

Why can't Yakit connect to the engine?▼

Yakit connects to the engine either by launching a local yaklang process automatically or by connecting to a remote engine's gRPC address. If connection fails, verify the engine process started correctly or that the remote host:port gRPC address is reachable.

What are the differences between Yakit's three interface modes?▼

Security expert mode uses an icon bar suited for experienced penetration testers, classic mode uses a tree menu for beginners, and scan mode offers a simplified menu for batch scanning only. The mode is changed in system settings and alters the left menu and fixed tabs.