Home / Lab / Skills library
public resources / session release 01

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.

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

Frame · Skills
Frame 01 / the idea
16 workflowsShort instructions you can read, edit and reuse
4 themesStart with the job you need to finish
Your setupBring your own model, tools and permissions
Frame 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.

Frame the useful kit

Choose by the work.

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

S

Clear answer

Write & deliver

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

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

S

Keep my voice

Write & deliver

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.

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

S

Usable handoff

Write & deliver

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

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

S

Content to format

Write & deliver

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

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example 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.

S

Compact documents

Write & deliver

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.

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Research with receipts

Research & decide

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

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Buyer context

Research & decide

Researching an organization and a business role before preparing outreach.

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Questions that change the work

Research & decide

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

Bring

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

Returns

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

Example

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.

Limits

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

Advice

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

Example request

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

A

Existing data first

Research & decide

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

Bring

Required fields, freshness, source constraints and permitted services.

Returns

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

Example

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.

Limits

Includes no vendor integration, API key or endpoint subscription.

Advice

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

Example request

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

S

Check the actual page

Check & repair

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

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Reference-safe edits

Check & repair

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

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Image reading fallback

Check & repair

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.

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Release risk review

Check & repair

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.

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Recurring brief

Run & learn

Producing an authorized recurring operational or research brief.

Bring

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

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

A

Recover work context

Run & learn

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.

Returns

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

Example

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

Limits

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

Advice

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

Example 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.

A

Evidence retrospective

Run & learn

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.

Returns

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

Example

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

Limits

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

Advice

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

Example request

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

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.

made at meow creative haus · public kit v1.0 · back to the lab

Have something in mind?

Let's make it worth exploring.

Tell us what you need, who it is for and what already exists. A few clear sentences are enough to begin.

mewdiaservice@gmail.com