A community pottery studio prepares a monthly newsletter introducing its next classes and summarizing registrations. Its editor already uses chat to revise sentences but does not know how a skill differs from a one-off prompt or how spreadsheet figures should support the article. Use fictional class notes and a redacted practice table to learn one reusable method, draft the newsletter, check its figures and hand the work to another editor. The deliverable is a traceable article and a process that can be repeated next month.
Start with a method and a specific assignment
A skill usually provides an instruction file and may include scripts, templates and references. It can preserve a recurring method, but the editor still supplies this task's audience, materials and acceptance conditions. Describe the assignment: introduce a weekend pottery class to new community participants, identify the date, location, materials and registration action, and use only confirmed information. Ask for missing information to be listed separately. Have the assistant restate the task before choosing writing, data inspection or document-generation capabilities.
Prepare three separate inputs. A class fact card records confirmed dates and the responsible organizer. A practice registration table contains anonymous class identifiers, registrations, attendance and month. A writing task card sets the audience, length, voice and limits on interpretation. Preserve original inputs and write artifacts elsewhere. Ask the assistant to identify the skill being used, materials read and intended output. This helps distinguish a package being discovered from actual invocation and a correct result.
For discovery assistance, check whether SkillPI Skill Finder is present. If not, read its official repository instructions and install and enable it using the current host's supported method. Search against the studio newsletter task and ask for sources, versions, prerequisites and reasons for fit. Inspect the package and supporting files before adopting a candidate. A name or activity count cannot establish the result on the editor's machine. Trial a short, labeled sample first.
Record the selected source, revision, installation location and required tools. Check the host's loading scope and same-named items, and preserve the package structure so referenced resources remain available. Installation establishes that files are in place. A task-card-compliant result supplies evidence for this invocation. When a dependency or configuration fails, preserve the error and locate its stage rather than repeatedly overwriting working setup.
Draft from a fact card before polishing language
Build an outline from the supplied class description. The opening explains who the class is for, the middle describes what participants will do, and the ending gives the date, materials, location and registration action. Tie checkable statements to the fact card. Keep a missing fee or capacity in the questions list instead of inventing a value. Practice data should never become a quotation attributed to a real participant. Review information order before sentence-level changes.
For a passage-based style review, Writing Guidelines is a candidate for the revision stage. The verified listing describes selecting files, retrieving the linked handbook and returning findings with file and line locations. Confirm handbook access and explain the studio's audience and voice. Its technical-prose guidance needs interpretation for this newsletter and language. Style review is separate from checking class dates, credentials or statistical statements.
Put a repeated promotional sentence and an ambiguous registration action into the practice draft. Ask the reviewer to locate each issue, explain its effect and suggest a change. The editor chooses which suggestions to adopt and keeps before-and-after versions. For email and social versions, reuse the same fact card while adapting the opening, paragraph length and action sentence. Verify that shortening has not removed a condition or changed the date or location. A headline should describe the material without promising an unsupported outcome.
Define the table before interpreting a report
Write the field definitions first. Specify whether a registration means a successfully reserved place, how attendance was recorded and how cancellations or duplicates are handled. Keep stable activity identifiers and preserve the raw table. Create a small example with known answers: one class has ten registrations and eight attendees; another has twenty registrations and ten attendees. The total is eighteen attendees from thirty registrations, so the combined attendance fraction is eighteen divided by thirty. Averaging the two class percentages gives a different quantity. Label every number as rehearsal data.
Exploratory Data Analysis can help inspect the redacted CSV before reporting. Its verified listing describes bounded aggregate checks on supported local inputs, including missingness, unusual values and distributions. Core tools require Python 3.11 or newer; optional formats have additional prerequisites. Read the pinned scope before execution. Use it to examine table structure and quality, not as a promise to process any Excel workbook or generate every desired chart automatically.
Require the report to state which rows were covered, whether a limit was reached and which groups remain unseen. Keep original data unchanged. Unsupported formats need an approved export into a supported form. A missing attendance value is not automatically zero. Mark it, calculate the known portion under a stated denominator and retain the unresolved count. Investigate unusual records before excluding them. Use the existing spreadsheet tools for the final aggregation and a simple comparison of registrations and attendance, labeled with period, units and coverage. Exploration can reveal a question; it cannot establish that publicity caused a change.
Connect the narrative to checked figures
Produce a result table and compare it with the labeled example and field definitions. Only then ask the article to use a verified total or proportion. Identify rehearsal data and avoid presenting incomplete groups as a complete population. Each quantitative sentence should lead back to a table or calculation. Before comparing months, check whether the number of classes, schedule and recording method are comparable. Explain changed conditions instead of assigning the difference directly to a post or campaign.
Hand off both newsletter variants, field definitions, input revisions, calculations, chart and revision notes. Ask another editor to recompute one total and locate the source of one date using only that package. Repair a missing evidence link before sending it onward. Publishing follows the team's separate procedure; a generated draft is not a sent newsletter. Next month, update the facts and time range and replay the small example. After a skill or host upgrade, inspect output differences and retain a known working revision. Refresh candidate links against a new capability gap when the workflow needs it.
Common questions
Can someone who does not code begin?
Start with a clear input-output task such as reviewing one passage and follow the host's setup instructions. Scripted analysis needs a runtime. Ask a maintainer to explain unfamiliar commands, establish file access and trial synthetic material before expanding use.
Will a skill complete every part automatically?
It supplies a method and resources, while the host, tools and materials determine what can execute. The editor confirms facts, scope and results and checks that promised files exist. Keep a suggested action separate from an executed result.
Does open source mean free execution and fewer tokens?
Review the particular license, model usage and external services. Installation and execution have different costs. Record calls and rework on this task; a saving needs a comparable baseline.
Can the workflow move to another agent?
Check loading locations, supported metadata, scripts and tool interfaces on the destination. Reuse the short draft and known-answer table to verify discovery, invocation and output. General instructions can transfer without proving that every component works unchanged.
Where should a missing-skill investigation start?
Record the host version, working directory, loading scope and file format, then check name conflicts and dependencies. Identify discovery, invocation or execution as the failing stage. Minimal steps and redacted errors make the next repair specific.