Artifact Profiles

Select artifact profiles independently from rigor depth. More than one profile may apply.

Academic Paper Or DOCX/PDF Submission

Check:

Prompt and rubric coverage.
Due date or submission deadline. Treat recurring patterns as hypotheses to verify against the prompt, rubric, title page, course calendar, or project schedule.
Required citation style: title page, abstract/keywords if required, headings, page numbers, margins, line spacing, paragraph indents, references, figures, tables, appendices, and cross-references.
Source integrity: every in-text citation has a reference, every reference is cited, authors/years/titles match source pages, DOIs/URLs resolve when checked, and non-scholarly sources are not treated as peer-reviewed evidence.
Required tables and figures are introduced and discussed in body text.
Quantitative/statistical claims: test choice, assumptions, notation, p values, confidence intervals, effect sizes, sample scope, and causation limits.
No unintended metadata when tools permit checking: tracked changes, comments, hidden text, custom XML/properties, author/company/template data, and stale embedded object metadata.

Check:

Source provenance and why each source belongs.
Omissions against the assignment, research question, and likely output sections.
Tensions across sources, not just agreement.
Accuracy of summaries, dates, methods, results, and quoted/paraphrased claims.
Transfer: whether the compendium gives enough evidence to produce the target artifact without fresh searching.
Organization: source matrix, themes, evidence clusters, and source-to-claim usability.

Check:

Purpose and fit for the task.
Origin and authority of each source.
Timeliness and whether older foundational sources are supplemented.
Accuracy and method, including methodology labels and limits.
Transparency and traceability: DOI, URL, publisher page, stable locator, and citation completeness.
Objectivity and bias, especially vendor, advocacy, industry, or non-peer-reviewed sources.

Check:

Slide claim provenance and source notes.
Missing assignment, audience, or delivery requirements.
Tensions or caveats hidden by visual simplification.
Accuracy of facts, figures, chart labels, citations, and speaker notes.
Transfer to presentation use: sequence, narrative, accessibility, and audience comprehension.
Organization, slide density, visual hierarchy, and export readiness.

Check:

Problem fit and requirement traceability.
Omissions in edge cases, tests, security, deployment, operations, and rollback.
Tensions between architecture, constraints, user workflows, cost, and maintainability.
Accuracy of assumptions, API claims, configuration, commands, and test results.
Transfer to implementation or production use.
Organization of files, boundaries, naming, and reviewability.

Check:

Trigger clarity and no overbroad activation.
SKILL.md frontmatter validity.
Progressive disclosure: main skill concise, detailed guidance moved to references.
Public hygiene: no secrets, private paths, private project facts, or unintended generated artifacts.
Install instructions and examples.
No hidden scripts or network behavior unless documented.
Validation instructions and package boundaries are clear.