← the labpublic resources / session release 01
01 / the idea

good habits, in small files

i kept asking for the same corrections. keep my voice. put the answer where i can use it. open the actual page. those patterns became a kit other people can adapt.

16 workflows

Short instructions you can read, edit and reuse

4 themes

Start with the job you need to finish

Your setup

Bring your own model, tools and permissions

A three-chapter introduction. The full library is below.

a small first task

borrow one resource

A skill is a resource: a compact piece of operating knowledge you can inspect, adapt and carry between tools. Choose one below, download its file, then attach it to a bounded AI task with your own inputs.

Want to install it?

Save the file as SKILL.md inside a folder named after the skill. Import that folder using your app’s skill support. Loading behavior varies by app; confirm the assistant can see the instructions. Downloading alone does not install anything.

These are tool-neutral instructions. Browser, OCR and document workflows need the corresponding tools. Nothing here adds an account, integration or scheduler.

Download all 16 resources ↓

choose by the work

the useful kit

S = core utility in my setup · A = useful for a particular task · personal tiers, not quality scores · every file is a resource to edit

16 of 16 skills

Write & deliverS

Clear answer

Make a dense answer easy to act on without dropping the important uncertainty.

When to use it + example

Use it when

A status update, technical explanation or recommendation needs a concise answer.

Bring

The question, audience, available evidence and any length constraint.

From my work patterns

A software team asks whether a release is done. The response distinguishes a passing build from a live page that still needs checking.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Concision must not conceal uncertainty or replace a requested detailed analysis.

My advice

Use this for work updates. Supply your own voice sample when you want personality; there is no required character or catchphrase.

Try this request

Explain the current release state to a non-engineer. Keep the evidence and the exact next action. State anything you did not verify.

What comes back

A direct answer, the necessary evidence and a concrete next action when one exists.

Download skill ↓ plain Markdown
Write & deliverS

Keep my voice

Edit the draft while keeping the person who wrote it recognizable.

When to use it + example

Use it when

A supplied draft needs clarity, a lighter edit or adaptation to a named audience.

Bring

The draft, audience, destination and optional examples of the writer's own prose.

From my work patterns

A founder's rough technical note becomes a short public post. The specific observation stays; the repeated setup goes.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

An editing pass cannot establish authorship or guarantee that a detector will classify text a particular way.

My advice

Give it a real draft. A request to sound human is less useful than two paragraphs you actually wrote.

Try this request

Edit this draft for an industry newsletter. Keep my uncertainty and conversational rhythm. Add no facts. Return one final version.

What comes back

The complete edited draft and a short explanation of substantive changes.

Download skill ↓ plain Markdown
Write & deliverS

Usable handoff

Put the answer, artifact and next action where the recipient can use them.

When to use it + example

Use it when

Delivering instructions, code, copy or files whose location or next step could be confusing.

Bring

The completed work, intended recipient, available files and destination.

From my work patterns

An education team's caption and image export are delivered together, with the final caption in chat and one clearly labelled image file.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Do not paste secrets or bulk private records to make a handoff self-contained.

My advice

Say who receives the handoff. The person running a command needs different detail from the person approving a design.

Try this request

Package this completed work for the person who will publish it. Give one final copy block, file links and the remaining checks.

What comes back

A usable final answer, verified artifact links and the smallest necessary next step.

Download skill ↓ plain Markdown
Write & deliverS

Content to format

Turn supported ideas into a post or carousel with a clear reading sequence.

When to use it + example

Use it when

Adapting notes into a named social format with defined dimensions or slide count.

Bring

Source notes, audience, platform, brand constraints and requested format.

From my work patterns

A technical note for an enterprise software audience becomes a carousel. A different education example changes the audience and evidence, not just the logo.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

This skill supplies a workflow, not platform access or a promise of reach.

My advice

Name the reader and one takeaway before asking for ten slides.

Try this request

Turn these notes into a six-slide square carousel for operations managers. Label invented examples and keep the source claims intact. Do not post it.

What comes back

Final copy, the requested visual sequence, caption and evidence notes where needed.

Download skill ↓ plain Markdown
Write & deliverS

Compact documents

Build readable documents with an explicit page budget and visual QA.

When to use it + example

Use it when

Creating a brief, report or presentation where density and export quality matter.

Bring

Content, intended use, brand reference, page size and page budget; use three pages when no budget is specified.

From my work patterns

A long operations report becomes three pages: findings, comparison and next actions. The explicit ten-slide social request remains ten slides.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

A rendering tool is required to certify visual QA. Text extraction alone does not verify layout.

My advice

Three pages is this pack's editable default. Change it for a different publication requirement.

Try this request

Make a three-page decision brief from these notes. Prioritize readable comparisons and inspect each rendered page before delivery.

What comes back

The requested document, a brief QA result and any explicitly unresolved constraints.

Download skill ↓ plain Markdown
Research & decideA

Research with receipts

Find evidence for a decision and keep unavailable or conflicting sources visible.

When to use it + example

Use it when

A question needs current information, source comparison or verification of a claim.

Bring

The question, decision criteria, date sensitivity and any required sources.

From my work patterns

A browser research task produces useful answers from some services and blocked states from others. The final note preserves that distinction.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Requires access to the sources. A retrieval failure is not evidence that the claim is false.

My advice

Specify what would change your decision. More links are not automatically more useful evidence.

Try this request

Check this claim against current primary sources. Show where they agree, what remains uncertain and which pages you could not inspect.

What comes back

An evidence-backed answer with source links, dates where relevant and unresolved conflicts.

Download skill ↓ plain Markdown
Research & decideA

Buyer context

Prepare a relevant buyer brief and grounded outreach draft.

When to use it + example

Use it when

Researching an organization and a business role before preparing outreach.

Bring

The target industry or organization, buyer role, real offer and permitted sources.

From my work patterns

An enterprise software offer gets different messaging for a technical owner and a procurement lead, based on their responsibilities.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

No bundled prospect database or contact enrichment. Relevance is not a measured reply-rate improvement.

My advice

Start with an offer you can substantiate. Personalization cannot repair a vague service claim.

Try this request

Research this organization using public business sources. Prepare a buyer brief and one outreach draft. Label assumptions and do not send anything.

What comes back

A short qualification brief, supporting sources and an unsent outreach draft unless sending was authorized.

Download skill ↓ plain Markdown
Research & decideA

Questions that change the work

Resolve consequential ambiguity without turning every task into an interview.

When to use it + example

Use it when

An unclear requirement could change scope, permissions, architecture or the final deliverable.

Bring

The request, existing decisions, constraints and available project evidence.

From my work patterns

A build discussion has many repeated skill reads within one session. The useful question settles the destination; another round of cosmetic questions would add little.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Do not require clarification merely because several acceptable implementation choices exist.

My advice

Use at the point of uncertainty. It need not be an always-on gate.

Try this request

Review this brief. Ask only questions whose answers change the result; choose sensible defaults for reversible details.

What comes back

A brief set of necessary questions or a stated assumption followed by progress.

Download skill ↓ plain Markdown
Research & decideA

Existing data first

Check an existing export or endpoint before building another scraper.

When to use it + example

Use it when

A data collection task may already have an authorized API, dataset or export.

Bring

Required fields, freshness, source constraints and permitted services.

From my work patterns

Before scraping a business directory, a researcher checks whether an existing export contains the required fields. This is an illustrative workflow, not a verified endpoint success from the audit.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Includes no vendor integration, API key or endpoint subscription.

My advice

A source with fewer fields but clear provenance may be the better starting point.

Try this request

Before building a scraper, inspect available authorized exports or APIs for these fields. Compare coverage, freshness and cost without purchasing access.

What comes back

A source choice with field coverage, limitations and a reproducible access plan.

Download skill ↓ plain Markdown
Check & repairS

Check the actual page

Verify a web result in the named browser and distinguish local from live proof.

When to use it + example

Use it when

Checking a web change, a saved dashboard state or a specific page interaction.

Bring

The exact URL, expected behavior, browser preference and authorized actions.

From my work patterns

A homepage link works locally while its hosted preview requires sign-in. The handoff records both states instead of calling the release verified.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Requires browser access. It does not authorize purchases, messages, permission changes or unrelated live mutations.

My advice

Give the exact URL and one expected result. A screenshot without an action rarely proves the whole flow.

Try this request

Verify this page in the browser at desktop and mobile sizes. Test the primary link and report observed results separately from anything blocked.

What comes back

A concise verification receipt separating local, preview and production results.

Download skill ↓ plain Markdown
Check & repairA

Reference-safe edits

Change the requested document fields while preserving the established reference.

When to use it + example

Use it when

Updating a recurring invoice, statement, form or formatted business document.

Bring

The reference document, exact requested changes and authoritative replacement values.

From my work patterns

A monthly invoice changes the requested month and description while retaining the approved reference layout. Exported footer spacing is checked.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Document preparation is not accounting or legal certification and does not authorize payments.

My advice

Supply the actual reference and replacement values. Do not ask the model to reconstruct them from memory.

Try this request

Update only these fields in the attached reference. Recalculate affected totals, preserve the layout and inspect the exported pages.

What comes back

An updated document, field-level change summary and visual verification status.

Download skill ↓ plain Markdown
Check & repairA

Image reading fallback

Recover limited text or structure when ordinary image inspection is unavailable.

When to use it + example

Use it when

A model cannot directly read an image but authorized OCR or image-analysis tools are available.

Bring

The image, the specific question and the tools available locally or through approved services.

From my work patterns

A non-vision setup requests a fallback for image inspection. The audit established requests for this kind of help, not a measured recovery accuracy.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

OCR and pixel measurements cannot establish identity, intent or reliable meaning for every visual element. No accuracy claim is included.

My advice

Ask a narrow question such as reading a label. Do not treat this as a substitute for all visual reasoning.

Try this request

Recover the text from this image using available OCR. Mark uncertain characters and explain what the method cannot establish.

What comes back

Recovered text or measured structure, with uncertain regions and unanswerable parts identified.

Download skill ↓ plain Markdown
Check & repairA

Release risk review

Review the changed work for exposure, behavior regressions and an achievable rollback.

When to use it + example

Use it when

Preparing a scoped public release or reviewing a change that touches sensitive data or permissions.

Bring

The actual diff, release target, authorization, tests and rollback option.

From my work patterns

A static article builds successfully, but required review has not arrived. The release remains pending rather than bypassing the gate.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

This is a review workflow, not a security certification or independent approval.

My advice

Supply the diff and target. A generic checklist cannot prove that a specific release is safe.

Try this request

Review this change for release. Inspect the actual diff, relevant tests, exposure and rollback. Name blockers without changing permissions.

What comes back

A scoped release decision with evidence, blockers and a rollback action.

Download skill ↓ plain Markdown
Run & learnA

Recurring brief

Prepare a repeatable update that stays honest about stale or unavailable inputs.

When to use it + example

Use it when

Producing an authorized recurring operational or research brief.

Bring

The reporting period, sources, prior brief, decision owner and delivery scope.

From my work patterns

A weekly preparation run cannot reach a required integration. It returns a specific handoff and marks that section incomplete.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Includes no scheduler or integrations. Repeated execution is not proof that the automation is healthy.

My advice

Measure whether the brief supports a decision, not just whether the scheduled run finished.

Try this request

Prepare this week's brief from these sources and the prior report. Mark stale or missing inputs, and separate activity from completed outcomes.

What comes back

A dated brief with changes, evidence freshness, blocked inputs and actionable next steps.

Download skill ↓ plain Markdown
Run & learnA

Recover work context

Resolve references such as ‘that thing’ from the smallest relevant, authorized context.

When to use it + example

Use it when

A request depends on recent work that is missing from the current conversation.

Bring

The ambiguous request, approximate time or application and available permitted records.

From my work patterns

A request refers to a prior screen or unfinished draft. The assistant narrows the context before editing the wrong artifact.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Requires an existing permitted context source. This pack installs no recorder and enables no screen access.

My advice

A rough timestamp or filename can save a broad history search.

Try this request

Recover the context for this unfinished task from the named local records. Limit the search to this project and do not expose unrelated material.

What comes back

A short reconstruction of the relevant task with supporting references and unresolved ambiguity.

Download skill ↓ plain Markdown
Run & learnA

Evidence retrospective

Turn a recurring correction into a narrow improvement with an observable check.

When to use it + example

Use it when

Reviewing repeated work, a failure or a correction to improve the next run.

Bring

The intended outcome, actual artifact, verification evidence and relevant prior corrections.

From my work patterns

Repeated document bloat leads to an explicit three-page preference. Future checks inspect readability as well as page count.

Composite illustration, informed by the local audit. No client identity or measured outcome is implied.

A useful constraint

Self-review is not independent evaluation. Usage frequency alone cannot establish quality or improvement.

My advice

Prefer one correction tied to a real failure over another permanent checklist.

Try this request

Review this deliverable against the request and evidence. Identify one reusable improvement and how we would verify it on the next run.

What comes back

A brief retrospective with the observed issue, proposed correction and next-run verification.

Download skill ↓ plain Markdown

what became public

Clear answer generalizes the concise-answer habit. Voice editing also covers the cleanup role. Buyer context combines qualification and nurture preparation. The remaining workflows cover the research, browser, document, context and recurring-work patterns in the original audit.

The downloads are newly written public workflows. They do not redistribute private configuration files or third-party skill implementations.

reuse, with context

You may use, modify and redistribute these files, including commercially, with their included notice retained. They are provided as-is. That permission covers the new files, not third-party software or services.

Examples are composites and tiers are personal judgments. File validation checks structure; it does not establish effectiveness across models or prove time saved. Treat the first task as a trial you can inspect.