← All creators

leiverkus

User

Skill-driven research workflow for Claude Code: theology, biblical archaeology, ancient history, digital humanities. Methodology-aware (hermeneutic / quantitative / mixed) with SOFT-GATE audit trails and optional MCP integration.

18 indexed · 0 Featured · 1 stars · avg score 74
Prolific

Categories

Indexed Skills (18)

Code & Development Listed

drafting-manuscript

Use to draft a book chapter, article section, or grant exposé from synthesized wiki content. Pulls from stable synthesis pages and source pages, writes to `output/publication/**/*.qmd` with proper citations. Never drafts from memory — always from the wiki.

0 Updated 4 days ago
leiverkus
Code & Development Listed

executing-research-plan

Use AFTER writing-research-plan has produced a ready plan (status=ready for hermeneutic projects, status=pre-registered for quantitative/mixed). Reads `input/ideas/<slug>-plan.md`, creates TodoWrite items, and works tasks via subagent dispatch (source-ingester, analyst, drafter) with two-stage review. Does not execute anything outside the plan.

0 Updated 4 days ago
leiverkus
Data & Documents Listed

ingest-source

Use when adding a scholarly source (PDF, book chapter, article) to the research project wiki under a specific focus. Produces a focus-driven Source page (claims relevant to the project, not a generic summary), extracts Entities, updates BibTeX, and logs the ingest. On re-ingest of the same source with a new focus, appends a new focus block to the existing page rather than overwriting. This is the ONLY skill for bringing sources into the knowledge wiki.

0 Updated 4 days ago
leiverkus
Code & Development Listed

literature-review

Systematic literature search for theology, biblical archaeology, ancient history, and digital humanities. Triggers on "literature review on X", "Stand der Forschung zu X", "Literaturrecherche zu X". NOT for single-paper lookups — those are simple metadata queries.

0 Updated 4 days ago
leiverkus
Code & Development Listed

requesting-peer-review

Use when a manuscript (book chapter, article, grant) is drafted and ready for structured review. Runs a two-stage peer-review workflow — constructive then adversarial — with discipline-specific checklists (CONSORT/STROBE + theology/archaeology/DH-specific).

0 Updated 4 days ago
leiverkus
Code & Development Listed

wiki-lint

Use to validate the knowledge wiki — frontmatter completeness, broken wikilinks, orphaned pages, status consistency. Wraps `scripts/lint-wiki.py` from the research project template. Required before drafting and before finishing.

0 Updated 4 days ago
leiverkus
Code & Development Listed

scaffold-research-project

Use to create a new research project from the template via conversation — no terminal, no `cp` commands. Asks for project name, parent directory, methodology, discipline, and languages; copies the template tree using the Write tool; patches CLAUDE.md frontmatter; optionally initialises git. Designed to work in Cowork (no shell access) as well as Claude Code.

0 Updated 4 days ago
leiverkus
Code & Development Listed

wiki-graph

Use to build and analyse the knowledge wiki as a graph. Runs `scripts/wiki-to-graph.py` (from the research project template) to export an interactive self-contained graph.html (open in any browser, no install) plus graph.json / graph.graphml — and answers questions against the *live* wiki via deterministic query sub-commands (`neighbors`, `path`, `god-nodes`, `bridges`, `relations`, `search`, `stats`), grounded in the result — most-connected pages (god nodes), entities that bridge otherwise-unconnected sources, relation types and confidence (inferred vs grounded), clusters and weak spots. Triggers include "build/show me a knowledge graph", "map the wiki", "graph view of my research", "which entity connects or bridges my sources", "what are the most connected or central pages", "find surprising connections", "where are the gaps or weak links in the wiki", "export the wiki to Gephi/yEd". For frontmatter and wikilink validation use `wiki-lint`; for content and claim audit use `semantic-wiki-review`.

0 Updated 4 days ago
leiverkus
AI & Automation Listed

brainstorming-research

Use BEFORE any research work — defining a question, planning a study, starting a chapter, proposing a grant. Explores intent, state of the field, methodology, feasibility, and ethics, then writes a design doc and gets user approval.

0 Updated 4 days ago
leiverkus
Code & Development Listed

finishing-a-research-project

Use when a research project reaches completion — manuscript finalized, peer-review cleared, ready for publication / submission / archive. Runs the final checklist across rendering, BibTeX, wiki, data, reproducibility, archive, and follow-up grant planning.

0 Updated 4 days ago
leiverkus
Code & Development Listed

grant-finder

Use for researching German and European funding programs (DFG, ERC, VolkswagenStiftung, Gerda Henkel, Fritz Thyssen, bilateral DE-IL) for projects in theology, biblical archaeology, digital humanities. Produces a DFG-style research-status draft, funding ranking, panel recommendation, and BibTeX.

0 Updated 4 days ago
leiverkus
Code & Development Listed

semantic-wiki-review

Use when the user asks for a *content* review of the wiki — contradictions between pages, outdated claims overtaken by newer sources, weakly supported assertions, missing cross-references that the structural linter cannot detect. Distinct from `wiki-lint` (structural, deterministic, CI-gated).

0 Updated 4 days ago
leiverkus
Code & Development Listed

using-research-powers

Use when starting any research conversation — establishes how to find and use research skills. Requires Skill tool invocation before ANY response, including clarifying questions. Governs the full research workflow from idea to publication.

0 Updated 4 days ago
leiverkus
AI & Automation Listed

writing-research-plan

Use AFTER brainstorming-research has produced an approved design doc. Converts the design into a pre-registered research plan with falsifiable hypothesis, concrete task list, and verification criteria. No execution happens without this plan.

0 Updated 4 days ago
leiverkus
Data & Documents Listed

odg

Create, read, edit, convert, repair, inspect, or export OpenDocument Graphics/Drawing files (.odg). Supports diagramming: connectors with shape-to-shape binding, glue points, and shape groups for flowcharts, org charts, and mind maps.

1 Updated 1 weeks ago
leiverkus
Data & Documents Listed

odp

Create, read, edit, convert, repair, or inspect OpenDocument Presentation files (.odp) — including bidirectional conversion to PPTX/PPT via headless LibreOffice. Supports shape animations (entrance, exit, emphasis, motion paths), slide transitions, master-page customization, and a template ecosystem (curated branded designs + inspector/extractor tools).

1 Updated 1 weeks ago
leiverkus
Data & Documents Listed

ods

Create, read, edit, convert, repair, inspect, analyze, or format OpenDocument Spreadsheet files (.ods) — including bidirectional conversion to XLSX/XLS via headless LibreOffice. Supports named ranges, data validation (dropdowns and range constraints), embedded charts (bar, line, pie, scatter), conditional formatting, and pivot tables.

1 Updated 1 weeks ago
leiverkus
Data & Documents Listed

odt

Create, read, edit, convert, repair, or inspect OpenDocument Text files (.odt) — including bidirectional conversion to DOCX/DOC via headless LibreOffice and a template ecosystem (grant proposal, academic paper, letterhead, CV, dissertation). Includes scholarly authoring: footnotes, endnotes, citations (BibTeX/CSL-JSON), cross-references (bookmarks, reference-marks, figure/table sequences), MathML formulas (from LaTeX), and generated indexes (table of contents, bibliography, illustration/table index, alphabetical index).

1 Updated 1 weeks ago
leiverkus

Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.