Results for “staatsexamen”

Guides statistical hypothesis testing with assumption checks, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting for research data.

Run arbitrary Stata code or a .do file and display the result.

Run static analysis on a Stata .do or .ado file and report style and best-practice issues.

Look up Stata command documentation and display formatted help text.

Analysiert eigene JPA-Klausuren und erstellt eine gewichtete Themenmatrix mit Lernempfehlungen für die Examensvorbereitung, inklusive Fristen- und Risikoprüfung.

Classical end-to-end empirical analysis workflow in the traditional Stata ecosystem — native Stata + reghdfe + ivreg2 + csdid + did_imputation + eventstudyinteract + sdid + rdrobust + rddensity + synth + synth_runner + psmatch2 + teffects + ebalance + coefplot + esttab + asdoc + binscatter. **Defaults to economics empirical-paper style** (AER / QJE / AEJ) — every run produces a publication-ready output set with a multi-column regression table (M1→M6 progressive controls/FE) as the centerpiece, plus Table 1 (descriptives), mechanism / heterogeneity / robustness tables, and event-study + coefficient + trend figures. Covers the full 8-step Stata pipeline an applied economist runs on every paper — (1) data import & cleaning (use/import, destring, misstable, duplicates, merge assert), (2) variable construction (gen/egen/winsor2/xtile/xtset with L./F./D.), (3) descriptive statistics & Table 1 (tabstat/balancetable/asdoc), (4) classical diagnostic tests (sktest/swilk/hettest/imtest/xtserial/xttest3/vif/dfuller/kpss/

Audit datasets for structure, missingness, labeling, suspicious values, duplicate identifiers, and documentation readiness. Use when a researcher asks for data QA, codebook review, sanity checks, or pre-analysis cleanup guidance.

Comprehensive Stata reference for writing correct .do files. Covers syntax, options, gotchas, and idiomatic patterns. Use this skill whenever the user asks you to write, debug, or explain Stata code. Generates ready-to-run .do files for the user to execute manually.

Stress-test ideas, plans, and decisions using structured critical reasoning across five modes: Socratic questioning, dialectic, pre-mortem, red teaming, and evidence audit.

After scaffolded practice, run an unassisted check — a problem with no AI help. Separates what the learner can do with support from what they can do independently. Critical for preventing phantom attainment.

Analyzes state merit review for non-covered securities offerings, applying NASAA Statements of Policy to cheap stock, promoter equity investment, voting rights, and promoter compensation. Produces examiner-ready comment responses with cap table analysis and negotiation strategy. Use when filing Reg A, Rule 504, intrastate, or direct public offerings in merit review states, responding to Blue Sky examiner comments, structuring offerings to avoid conditioning, or analyzing NASAA SOPs. Also trigger on cheap stock analysis, promoter equity tests, unequal voting rights review, state examiner correspondence, or phrases like "merit review issues" or "the state examiner sent comments."

Bewertet juristische Klausurlösungen im Gutachtenstil, prüft Obersatz, Definition, Subsumtion und Ergebnis und gibt strukturiertes Feedback mit Verbesserungsvorschlägen.

Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implementation, or says "is this spec implementation-ready", "trace requirements to tasks", "/analyze", "spec sanity check", "spec readiness gate", "spec consistency check". Output: docs/reviews/YYYY-MM-DD-<slug>-spec-crosscheck.md.

Pressure-tests an ISMS with six sample-driven questions to prepare for ISO 27001 internal, certification, or surveillance audits.

last_updated: 2026-03-02T14:30:00Z

Fetch and display stored r(), e(), and s() results from the last Stata command.

Live-device iOS QA for SwiftUI apps. (gstack)

Promove o cumprimento de sentenca (titulo executivo judicial) — disposicoes gerais (CPC 513), titulos judiciais (CPC 515), cumprimento DEFINITIVO de pagar quantia com intimacao em 15 dias e multa de 10% + honorarios de 10% se nao pago (CPC 523 §1, penhora/avaliacao §3), demonstrativo atualizado do debito (CPC 524), cumprimento PROVISORIO sob recurso sem efeito suspensivo (CPC 520-522), alimentos com prisao civil (CPC 528 §3) e Fazenda Publica (CPC 534-535). Use quando o operador disser cumprimento de sentenca, executar a sentenca, intimar para pagar em 15 dias, multa de 10% cumprimento, cobrar sentenca transitada.

Creates a structured, queryable snapshot of a domain's current state, capturing entities, relationships, and properties with confidence scores and evidence anchors.

Tail, read, or search a Stata log file from a previous command or background task.

Write a rigorous, decision-grade experiment spec — falsifiable hypothesis, primary metric, guardrails, randomisation unit, exposure definition, method (A/B, holdout, switchback, quasi-experiment, MAB), MDE/duration plan, peek policy, validity threats, and pre-committed decision rule. Platform-agnostic. Load when the user has a candidate experiment and needs to spec it before launch, or says "spec this experiment", "write the test plan", "design this A/B test", "what's the hypothesis", "how big a sample do we need", "how long should we run this", "define the metrics for this test", or when the experimentation orchestrator routes here.

Stateful validator-gated research loop with native-hook persistence

Use to sign off a QA period for audit or governance — stating what is being attested to, on what evidence, and with which limitations. Trigger for "sign off the QA period", "attest to our quality results", "monthly QA governance pack", "certify the quality figures", or being asked to confirm quality was assured for a period.

Use this skill when the user asks specifically about preparing for the New Entrant Safety Audit (NESA) under 49 CFR 385 Subpart D — different from a Compliance Review. Covers what auditors look at, the 18-month window, automatic failure conditions, the 60-day fix window, what to NOT do, and how to convert from "new entrant" to permanent authority. Cite 49 CFR 385.301-321.

Use when selecting a statistical test with AI consultation, when assumptions need checking against the actual data, when an analysis plan or decision log must be written before running anything, or when results need APA-style reporting with effect sizes.

Scan and audit AI agent skills for security risks before installation, producing a PASS/WARN/FAIL verdict with findings and remediation guidance.

Read-only audit of unhappy-path UI states vibe-coding skips — empty, loading, error, offline, zero-results, permission, overflow — then plan fixes. Use when "check empty/error states", "audit loading states", or "what happens when this fails". Dead buttons → plan-stub-checker; backend timeouts → audit-resilience.

Simulates SSL stripping attacks using sslstrip, Bettercap, and mitmproxy in authorized environments to test HSTS enforcement, certificate validation, and HTTPS upgrade mechanisms.

Runs and writes tests for a project, supporting unit, integration, and end-to-end scopes, plus two-pass TDD orchestration with quality-gate checks and regression sweeps.

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

Prüft SaaS-AGB-Klauseln nach BGB §§ 305-310, trennt Einbeziehung, Transparenz und Inhaltskontrolle und liefert Klauselampel, Redline und Ersatzformulierungen mit gerichtsfester Begründung.

Use this skill to evaluate which DataQ challenges have winning evidence and which don't. Covers documented vs anecdotal evidence and the 8 high-success patterns.

Describe and summarize the current dataset in memory. Optionally inspect a specific variable with codebook.

Systematically QA test a web application and fix bugs found. (gstack)

Systematically QA test a web application and fix bugs found. (gstack)