Results for “pe-files”

Guide users building a personal CRM from simple files to structured database.

Creates and maintains persistent markdown planning files that survive session resets by hooking into Claude Code's lifecycle.

Saves, retrieves, and organizes personal notes locally as Markdown files in ~/.synapse/notes/.

Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.

Performs static analysis of Windows PE malware samples using PEStudio to examine file headers, imports, strings, resources, and indicators without executing the binary.

Analyze PyTorch profiler and vLLM trace files with Perfetto SQL evidence. Use when working with torch profiler traces, merged_trace files, vLLM profiling logs, Perfetto trace analysis, GPU kernel hotspots, synchronization waits, rank imbalance, prefill/decode bottlenecks, or optimization reports.

Creates CodeTour .tour files — persona-targeted, step-by-step walkthroughs that link to real files and line numbers for any repository.

Provides a persistent, queryable virtual filesystem backed by SurrealDB for AI agents, with a Rust core and a Python agent interface.

Parse and analyze Windows forensic artifacts including MFT, registry hives, prefetch files, event logs, LNK files, and jump lists using Eric Zimmerman's EZ Tools suite and KAPE.

This skill should be used when the user asks to "offload context to files", "implement dynamic context discovery", "use filesystem for agent memory", "reduce context window bloat", or mentions file-based context management, tool output persistence, agent scratch pads, or just-in-time context loading.

Calculates polygenic risk scores from 23andMe or AncestryDNA genotype files using PGS Catalog scoring files, then estimates population percentiles and risk categories.

Trains machine learning models on genomic interval data from BED files, including region embeddings, single-cell ATAC-seq analysis, and consensus peak building.

Create CodeTour `.tour` files with persona-targeted, step-by-step walkthroughs anchored to real files and line ranges for onboarding, architecture, PR review, and code explanation.

Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.

Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.

Use when performing genome arithmetic on interval files (BED, BAM, BEDGRAPH), including intersection, merging, coverage, format conversion, or sequence extraction.

Route one Paperclip child stage of the PLE new-content routine, producing hash-verifiable evidence and a fail-closed handoff.

Guides a conversation to design a new AI team member, generating agent identity files and optionally setting up performance reviews.

Deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments using the Adobe I/O CLI plugin.

Construye pipelines ETL/ELT con Pandas: extracción, transformación y carga de datos con logging, manejo de errores, idempotencia y opciones de orquestación.

End-to-end source processing -- seed, reduce, process all claims through reflect/reweave/verify, archive. The full pipeline in one command. Triggers on "/pipeline", "/pipeline [file]", "process this end to end", "full pipeline".

Analyzes malicious PDF files using PDFiD, pdf-parser, and peepdf to identify embedded JavaScript, shellcode, exploits, and suspicious objects without opening the document. Determines the attack vector and extracts embedded payloads for further analysis.

处理和分析用户上传的文件引用，提取关键信息并提供应用建议。适用于解析@符号引用、自然语言引用、提取短剧策划相关信息

Use when filtering Entrez search results by date, organism, publication type, sequence features, or other database-specific criteria in bioinformatics pipelines.

End-to-end data pipeline for empirical research: fetch economic data from APIs (FRED, World Bank, IMF, BLS, OECD, Yahoo Finance), clean and transform raw data, construct strategy-specific variables, and validate panel structure. Use when asked to fetch data, download data, clean data, merge datasets, prepare analysis-ready data.

Mine proof-heavy papers, notes, PDFs, Markdown, or LaTeX sources into source-indexed proof-material files. Use when the user wants to extract technically nontrivial lemmas, estimates, definitions, dependencies, reductions, constructions, or proof strategies, preserve paper locations and stable material IDs, run DeepSeek screening/backtests, and update the proof-material index rather than writing directly to proof-usage.

Deploys and monitors ransomware canary files across critical directories using Python's watchdog library for real-time filesystem event detection, triggering alerts via email, Slack, or syslog when decoy files are accessed.

Search, filter, and browse high-signal academic papers using the Paperzilla CLI.

Create IEP templates for individualized education. TRIGGERS - Use when user needs help with iep-template related tasks.

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc