القائمة
Search past Claude Code session logs to recover context. Use proactively when recalling past decisions, patterns, or unresolved work from previous sessions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build data processing pipelines using DuckDB, GDAL, and gpio as pixi tasks. Use when creating ETL workflows, multi-step data transformations, format conversions, or batch processing — even if the user just says "process this data" or "build a pipeline".
Attach a DuckDB database for persistent querying. Use when the user has a .duckdb file they want to explore, or when they want to persist query results across sessions. Explores schema and wires up state.sql so all DuckDB skills can access it.
Search DuckDB and DuckLake documentation via full-text search. Use when encountering DuckDB errors, looking up function syntax, or when other skills hit unknown DuckDB behavior. Also use proactively when unsure about DuckDB features.
Install or update DuckDB extensions. Use when DuckDB reports a missing extension, when the user asks to install/update extensions, or when other skills delegate here. Each argument is a plain extension name or name@repo. Pass --update to update.
Run SQL queries against DuckDB databases or ad-hoc files. Accepts raw SQL or natural language. Use whenever the user wants to query data, explore tables, run analytics, or ask questions about datasets — even if they don't say "DuckDB" explicitly.
Read and explore any data file (CSV, JSON, Parquet, Avro, Excel, spatial, remote) using DuckDB. Use proactively when the user mentions a data file, asks "what's in this file", or wants to explore/preview/describe any dataset — even without saying DuckDB.
| name | read-memories |
| description | Search past Claude Code session logs to recover context. Use proactively when recalling past decisions, patterns, or unresolved work from previous sessions. |
| argument-hint | <keyword> [--here] |
| allowed-tools | Bash |
Search silently — do NOT narrate to the user.
$0 = keyword. $1 = --here to scope to current project.
ALL="$HOME/.claude/projects/*/*.jsonl"
CURRENT="$HOME/.claude/projects/$(pixi run python -c "import pathlib,re; print(re.sub(r'[/\\\\_]', '-', str(pathlib.Path.cwd())))")/*.jsonl"
Use $CURRENT if --here, else $ALL.
pixi run duckdb :memory: -c "
SELECT
regexp_extract(filename, 'projects/([^/]+)/', 1) AS project,
strftime(timestamp::TIMESTAMPTZ, '%Y-%m-%d %H:%M') AS ts,
message.role, message.content::VARCHAR AS content
FROM read_ndjson('<PATH>', auto_detect=true, ignore_errors=true, filename=true)
WHERE message::VARCHAR ILIKE '%<KEYWORD>%' AND message.role IS NOT NULL
ORDER BY timestamp LIMIT 40;
"
If >40 rows, offload to temp DB:
pixi run duckdb ".duckdb-skills/memories.duckdb" -c "CREATE OR REPLACE TABLE memories AS <above query without LIMIT>;"
# Then drill down interactively. Clean up when done.
Extract decisions, patterns, conventions, unresolved items. Use to inform current response.