88 个 · 按相关度排序
Operational playbook for running cold email continuously. Prescribes what to do on Monday / Wednesday / Friday / biweekly / monthly / quarterly. Use this as your ongoing cadence once your first campaign is live. What separates hobbyist from top 1% operators isn't tooling — it's consistency. This skill is the schedule.
中文简介正在准备中。当前显示原文说明。
The weekly keep/cancel/promote/buy loop for a cold email sending fleet. Decides which domains are burned and should be cancelled, which warmed reserves to promote into campaigns, which capacity to demote, and how many new domains to buy — using measured reply, bounce, age and send-volume floors instead of gut feel. Use when asked "which inboxes should I cancel", "what should I replace this week", "my fleet costs too much", "I'm under my send goal", or as the Friday hygiene routine.
中文简介正在准备中。当前显示原文说明。
Weekly. Scores the week from the ledgers with a source path beside every number and never writes a number it did not count in a file this run. It names exactly two things and files both as cards, the one fix worth doing next week and the one thing to stop, and it replays every learned browser flow once, read only, so a drifted selector is found on a Friday rather than on a Tuesday morning a routine needed it.
中文简介正在准备中。当前显示原文说明。
Weekly, on a Friday, read only everywhere. Scores the week from the kit's own ledgers with a source path beside every number, cuts it by platform, framework, pillar, slot time, and post length, rewrites the drafting standards from that evidence and from nothing else, replays the browser flows the other routines depend on, and files exactly one thing to stop and one to do more of. It publishes only where you released the channel, never replies, spends only where you released it, never touches a credential, and never writes a number it did not measure.
中文简介正在准备中。当前显示原文说明。
Weekly, on a Friday, read only everywhere. Scores the week from the ledgers with a source path beside every number, replays the browser flows the other routines depend on, names one thing to kill and one thing to scale, and files both as cards. It sends only where you released the channel, spends only where you released it, never touches a credential, and never writes a number it did not count out of a named file this run.
中文简介正在准备中。当前显示原文说明。
Weekly, on a Friday, read only everywhere. Scores the week from the ledgers with a source beside every number, replays the browser flows the other routines depend on, names one thing to kill and one thing to scale, and files both as cards. It sends only where you released the channel, spends only where you released it, never touches a credential, and never writes a number it did not measure.
中文简介正在准备中。当前显示原文说明。
Weekly on a Friday, conditional browser lane. Scores the week from the ledgers with a source beside every number and an estimate nowhere, reads the review and rating movement off the member's own listing screens, replays the browser flows the weekday routines depend on, and names the one product change that would have removed the most tickets this week. It sends only where you released the channel, never posts, never resolves anything, spends only where you released it, and never touches a credential.
中文简介正在准备中。当前显示原文说明。
Weekdays, file work only, no browser at all. Reads every ledger, every queue file, and every run record since its cursor, turns the member's ticks into replied lines and closed cards, computes the first response and time to resolution clocks the Friday report is built from, folds the card inbox, re-renders the desk board, and writes the short morning brief the member opens first. It holds every outbound action unless you released the channel, and it never touches a credential.
中文简介正在准备中。当前显示原文说明。
Weekly, on a Friday, read only everywhere. Scores the week from the daily metrics ledger alone, with the screen and the date range beside every number, then writes the ranked paste ready list of what to change in the account next week. Each line names one change, the exact screen, the current value, the proposed value, and the evidence row it came from. It proposes no change it cannot source, it names no action it took because it takes none, and it spends only where you released it.
中文简介正在准备中。当前显示原文说明。
Deep Mobile Security Red Team persona. Executes OWASP MASTG procedures including APK/IPA decompilation, Frida dynamic hooking, biometric bypasses, and local database decryption.
中文简介正在准备中。当前显示原文说明。
Decompile Android APK, XAPK, JAR, and AAR files using jadx or Fernflower/Vineflower. Reverse engineer Android apps, extract HTTP API endpoints, trace call flows from UI to network layer, and analyze runtime behavior with Frida, network capture, JNI/SO inspection, and signature generation. Use when the user wants to decompile, analyze, hook, inspect network traffic, bypass SSL pinning for analysis, locate crypto or signing logic, or follow call flows in Android packages.
中文简介正在准备中。当前显示原文说明。
Android and iOS application security testing — static and dynamic analysis, APK/IPA inspection, OWASP MASVS/MASTG verification, secure-storage and transport review, and mobile malware triage for authorized assessments
中文简介正在准备中。当前显示原文说明。
Use when reverse engineering tools are missing, not working, or need configuration. Installation guides for radare2 (r2), Ghidra, GDB, QEMU, Frida, binutils, and cross-compilation toolchains. Keywords - "install radare2", "setup ghidra", "r2 not found", "qemu missing", "tool not installed", "configure gdb", "cross-compiler"
中文简介正在准备中。当前显示原文说明。
Use when pentesting an Android/iOS app — Frida 17 instrumentation, SSL-pinning & root/jailbreak bypass, Android 14/15 CA injection, exported-component/content-provider abuse, deep-link/WebView chains, biometric bypass, Flutter/React-Native RE
中文简介正在准备中。当前显示原文说明。
Use when reverse-engineering a binary or firmware — static triage + decompilation (Ghidra/IDA/Binary Ninja), dynamic instrumentation (GDB/Frida 17/angr), anti-reversing & packer bypass, OLLVM/VM deobfuscation, UEFI/BIOS RE & Secure Boot research, patch-diffing for n-days
中文简介正在准备中。当前显示原文说明。
Android APK reverse engineering: unpacking, Java decompilation, smali modification, repacking and signing, Frida dynamic hooking, and native .so analysis with jadx, apktool, adb, and related tools.
中文简介正在准备中。当前显示原文说明。
Spark Studio's team-culture Relic — a 5-person AI product startup that existed 2022–2025: roast first then work, hotpot on Fridays, used Feishu while cursing Feishu daily, requirements always changing but versions always shipping. 星火工作室（Spark Studio）的团队文化 Relic。一个 2022-2025 年间存在过的 5 人 AI 产品创业团队： 先吐槽再开工，周五点海底捞，用飞书但天天骂飞书，需求总在变但总能把版本扛上线。
中文简介正在准备中。当前显示原文说明。
Use when generating weekly GTM performance reports, summarizing pipeline activity, reviewing outreach metrics, or creating executive updates. Triggers: 'weekly report', 'GTM report', 'pipeline review', 'weekly update', 'outreach summary', 'Friday report'.
中文简介正在准备中。当前显示原文说明。
Weekly marketing audit and operating review. Pulls the last 7 days of source-backed marketing, analytics, content, paid media, lead, watcher, and audit data; compares it to the prior 7 days; flags urgent issues; and produces a weekly scorecard plus action list. Use when "weekly audit", "weekly marketing review", "weekly check-in", "weekly scorecard", "what changed this week", "Friday marketing review", or any request for a recurring 7-day marketing audit.
中文简介正在准备中。当前显示原文说明。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift runtime behavior, inspect Keychain or plist state, bypass pinning, analyze deeplinks or universal links, or replay accepted iOS requests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
中文简介正在准备中。当前显示原文说明。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Android APK hooking, Frida tracing, request-signing recovery, SSL pinning bypass, JNI boundary inspection, and app trust-boundary analysis. Use when the user asks to hook an APK, inspect signer logic, trace Java or native boundaries, bypass pinning or root checks, inspect shared prefs or app databases, or replay accepted mobile requests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
中文简介正在准备中。当前显示原文说明。
Use weekly to find and ship one new automation. Walks the 3Ms interview — Mindset (find the candidate) → Method (scope one) → Machine (build it). Trigger on "let's level up", "what should I automate next", "find me leverage this week", or as a Friday ritual. One run = one shipped artifact.
中文简介正在准备中。当前显示原文说明。
Use for a weekly operating review (Friday wrap or Monday plan) — review progress against the 90-day priorities, surface stalled open loops, and set next week's focus. This is the PERSONAL operating review; distinct from /audit (checks the kit's connections/freshness) and /level-up (finds one automation to build). Trigger on "/weekly", "weekly review", "weekly planning", "how did this week go", "plan my week".
中文简介正在准备中。当前显示原文说明。
Detects authentication and biometric bypass vulnerabilities in mobile apps (Android/iOS). Trigger on: BiometricPrompt, LocalAuthentication, LAContext, evaluatePolicy, CryptoObject, Android Keystore, Secure Enclave, kSecAccessControlBiometryCurrentSet, userAuthenticationValidityDurationSeconds, confirmCredentials, biometric fallback, PIN bypass, passive authentication, enrolled biometrics detection, Frida hook auth, jailbreak bypass, TouchID, FaceID, fingerprint. Covers MASVS-AUTH-1/2/3.
中文简介正在准备中。当前显示原文说明。