تشغيل أي مهارة في Manus بنقرة واحدة

llm-wiki

النجوم٥

التفرعات٤

آخر تحديث٨ يوليو ٢٠٢٦ في ٢٠:٣١

Consult Stefano's compiled OKF knowledge bundles at ~/llm-wiki (the "second brain"). TRIGGER whenever a question falls in an existing bundle's domain — currently div-free-amr; numerical divergence constraints (∇·B=0, incompressibility), constrained transport and flux-CT, projection/divergence-cleaning, eight-wave, staggered vs collocated grids, discrete divergence/curl operators, SBP, mimetic/compatible/structure-preserving discretizations, DEC, block-structured AMR refinement interfaces, prolongation/restriction commutation. Also trigger on explicit mentions: "llm-wiki", "second brain", "check the wiki", "what does the wiki say". Use for CONSULTATION from any directory; ingestion/compilation work happens in ~/llm-wiki under its own CLAUDE.md.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

szaghi

szaghi/dotfiles

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

علماء الفيزياء الآخرونعلوم الحياة والطبيعة والاجتماع·SOC 19-2099

SKILL.md

readonly

name

llm-wiki

description

Consulting the LLM wiki

The bundles live at ~/llm-wiki/<bundle>/wiki/ (OKF v0.1: markdown + YAML frontmatter). Current bundles: div-free-amr.

Protocol

Enter at the catalog. Read ~/llm-wiki/<bundle>/wiki/index.md, follow links; navigation is the query engine. For symbol/term lookups, Grep the bundle (tags in frontmatter, math symbols like $P_D$ , aliases).
Notation is registry-defined. wiki/notation.md is normative; when quoting wiki math, keep its symbols. Per-paper symbol translations are in each Source page's # Notation map.
Respect claim kind. Frontmatter status: established = published result; status: hypothesis = claim a published source could overturn — report it as such, never as literature fact.
Cite pages. Answers grounded in the wiki cite the concept page(s) and, for provenance, the Source pages they rest on (wiki/sources/*.md, which carry DOIs and local PDF paths for going deeper).
Coverage is partial. Compilation is incremental — check ~/llm-wiki/tools/worklist.sh <bundle> (or wiki/log.md) before treating absence of a page as absence of literature. If the wiki lacks the answer, say so explicitly and fall back to the PDFs or general knowledge, labeled as such.
Read-only from outside. Never edit bundle content from another project's session. Gaps worth compiling: suggest an ingestion, to be run in ~/llm-wiki under its constitution (~/llm-wiki/CLAUDE.md).

المزيد من هذا المستودع

نفس المستودع

fobis

szaghi/dotfiles

Expert knowledge of FoBiS.py (Fortran Building System for poor men) — an automatic Fortran build tool that resolves module dependency hierarchies without manual makefiles. Use this skill whenever the user asks about: writing or editing a fobos file; running any fobis subcommand (build, clean, fetch, install, rule, doctests, scaffold, check, test, coverage, tree, introspect, run, cache, commit); Fortran project build configuration; diagnosing FoBiS build errors; adding GitHub dependencies to a Fortran project; the --json output flag; multi-mode builds; templates; variables and varsets; library builds (static/shared); MPI/OpenMP/coarray/OpenMP-offload builds; feature flags and conditional compilation; build profiles; the build cache; external-library auto-detection and pkg-config (.pc) generation; multi-target builds; convention-based source auto-discovery; the lock file and semver dependency constraints; the first-class test runner and coverage reports; LLM-assisted commit messages; the cflags-heritage feature

2026-07-085

blog

szaghi/dotfiles

Write and review technical developer blog posts as version-controlled markdown. Use this skill when the user wants to draft, write, or review a blog post / dev write-up / release note / tutorial about their code — typically HPC, Fortran, Python, or scientific-computing work. Orchestrates a draft pass and two verification agents: blog-code-checker (verifies every code block, command, and API claim against the real repos under ~/fortran and ~/python) and blog-prose-reviewer (strips AI tells and enforces technical voice). Output is a single markdown file under ./posts/ with minimal YAML frontmatter. Trigger on "/blog", "write a blog post", "draft a post about <repo/feature>", or "review this post". Do NOT trigger for academic manuscripts — use scientific-writing for those.

2026-06-245

darktable-operator

szaghi/dotfiles

Operator workflow for post-processing a RAW shoot in darktable with Claude as the operator. Use when the user wants to develop/process/batch their RAW photos (NEF/CR2/ARW), cull a shoot, apply a consistent look across a series, control edit values (exposure etc.) from the prompt, or run darktable-cli batches. Drives the four-stage pipeline (ingest/diagnose -> cull -> look -> export) and the edit-and-look QA loop. References the darktable-raw skill for module specifics. Architecture: the user builds a base LOOK once in the GUI; Claude captures it as a reference XMP and then controls precise per-module values from the prompt by patching the XMP (dt-xmp-patch.py), applying it headlessly via darktable-cli's positional-xmp arg.

2026-06-185

darktable-raw

szaghi/dotfiles

Knowledge base from the darktable 4.6 user manual. Use when developing RAW photos (NEF/CR2/etc.) in darktable, driving darktable-cli for headless/batch export, reasoning about the scene-referred pixelpipe, modules (exposure, filmic rgb, color calibration, highlight reconstruction, tone equalizer), masking/blending, styles & XMP sidecars, or color management. Version-matched to darktable 4.6.

2026-06-185

markitdown

szaghi/dotfiles

Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.

2026-06-155

generate-image

szaghi/dotfiles

Generate or edit images using AI models (FLUX, Nano Banana 2). Use for general-purpose image generation including photos, illustrations, artwork, visual assets, concept art, and any image that is not a technical diagram or schematic. For flowcharts, circuits, pathways, and technical diagrams, use the scientific-schematics skill instead.

2026-06-155

name

llm-wiki

description

Consulting the LLM wiki

The bundles live at ~/llm-wiki/<bundle>/wiki/ (OKF v0.1: markdown + YAML frontmatter). Current bundles: div-free-amr.

Protocol

Enter at the catalog. Read ~/llm-wiki/<bundle>/wiki/index.md, follow links; navigation is the query engine. For symbol/term lookups, Grep the bundle (tags in frontmatter, math symbols like $P_D$ , aliases).
Notation is registry-defined. wiki/notation.md is normative; when quoting wiki math, keep its symbols. Per-paper symbol translations are in each Source page's # Notation map.
Respect claim kind. Frontmatter status: established = published result; status: hypothesis = claim a published source could overturn — report it as such, never as literature fact.
Cite pages. Answers grounded in the wiki cite the concept page(s) and, for provenance, the Source pages they rest on (wiki/sources/*.md, which carry DOIs and local PDF paths for going deeper).
Coverage is partial. Compilation is incremental — check ~/llm-wiki/tools/worklist.sh <bundle> (or wiki/log.md) before treating absence of a page as absence of literature. If the wiki lacks the answer, say so explicitly and fall back to the PDFs or general knowledge, labeled as such.
Read-only from outside. Never edit bundle content from another project's session. Gaps worth compiling: suggest an ingestion, to be run in ~/llm-wiki under its constitution (~/llm-wiki/CLAUDE.md).