Improve a recurring AI activity through its results
Revisit sources, method and connections when the activity's usefulness changes.
When an automation keeps running but its context, sources or intended recipient have changed.
Competence · Method and learning · Public edition 0.3.2
A weekly search keeps returning sources already known. Compare what actually changed and what its recipient needs to decide.
The key relationship. Understands why an activity creates useful knowledge, repeats unused output or encounters new possibilities, then forms an appropriate continuation.
An illustrative situation to adapt to your work. Read the complete cases ↓
You supply the context: research, a service, a creative project or a team’s work. Examples make the method visible; adaptation preserves the relationships that make it work while understanding the purpose, sources, people and means of your own assignment.
Tell your AI what you want to achieve, what already exists and a practical situation to address. Ask how this competence changes the work and which knowledge from your domain should participate. MAIOS provenance identifies the shared knowledge; you can use it directly in your AI or compose it with an existing kernel.
Adaptation examples in other contexts ↗An activity can execute its prompt correctly while becoming less useful. The problem may lie in its sources, method, recipient or connection to the project.
This competence takes the activity itself as its object: it understands the differences it produces and how continuation could improve. It complements Meta-Activity when an existing recurring activity needs reconsideration.
Read the activity's purpose, current configuration, sources, means and recipient. Use a real result or project change: repeated output, lost access, missed possibilities, successful contributions or overlap. A fired schedule does not prove completed work, and silence does not prove uselessness. Reconsider the activity when a material relation changes.
Follow the path from source to result and use. Distinguish information seen, prepared, stored, received and exercised. A report in a folder does not prove that its recipient read it. Value can mean a better question, a prepared decision, an avoided error or a retained possibility. Unknown use is not zero value.
If knowledge is missing, deepen the relevant method. If it exists but is not used, repair the entry or recipient connection. Compare purpose, sources and consequences before combining overlapping activities. A better source, cadence or stopping condition may suffice. Preserve the original purpose and valid decisions.
When repeated reports appear saturated, the limit may belong to the repeated question. Look for a capability, relation, tool or condition that would change what the next run can do. Preparing a recipient to use a result can matter as much as finding another source. Develop a situated possibility without multiplying tasks merely to show improvement.
Correct the method within authorized work. Changing a schedule, pausing or deleting an activity requires the actual mandate and controller. Preserve concurrent changes and read back saved effects. New instructions represent a change; later runs and their consequences show whether it participates. Do not retire useful work merely because it produces no notifications.
Return the smallest meaningful difference to the recipient, preserving source, meaning and reentry conditions where needed. Retain why the activity's method changed. If experience corrects how usefulness, saturation or overlap is understood, update this competence. A deferred possibility can remain available without creating another job.
These cases illustrate situations, causal distinctions and choices you can adapt to your work.
Italiano. The following cases illustrate how the method is used.
A weekly search keeps returning sources already known. Compare what actually changed and what its recipient needs to decide. Source memory and a more precise question may correct the method without increasing frequency.
An activity produces useful notes, but the team works from another guide. Connect the result to that real entry and preserve the difference that changes a choice. Updating the file does not yet demonstrate the team’s use.
Two searches cover similar topics but serve different decisions. Clarify recipients and differences before merging them. They may share acquisition and retain separate interpretation, or one may absorb the other’s entire function within the entrusted mandate.
Use SKILL.md or START_CHAT_EN.txt with the relevant sources and your actual context. Keep observations, interpretations and what remains open distinguishable. Preserve the useful reason and continuation in the project’s guide.
Understands why an activity creates useful knowledge, repeats unused output or encounters new possibilities, then forms an appropriate continuation.
Inspect a real run or a changed field when the activity's own fitness becomes material. A quiet run or no immediate consumer does not prove zero value. Useful consequences can include a better question, retained opportunity, avoided wrong effect, practical recipient use or reduced duplication. Unconsumed output is potential rather than verified benefit. Preserve unknowns when observation is insufficient.
If the domain result exists but never reaches its consumer, repair receiving access or routing. If the method is weak, deepen its competence. If activities overlap, understand which owner can carry the useful function; do not merge merely because labels resemble each other. Trigger, recipient, sources, stop conditions and deduplication can evolve when actual consequences change their suitability. Return a small decision-changing relation rather than an entire report.
When repeated optimization appears saturated, consider the enabling relation that would change what the next action can do: practical knowledge, a reachable source, prepared receiving environment or a different question. Build that contribution at its owner when selected. Do not create another meta-auditor, require endless ideation or reopen valid closure. Integration, justified no-change, replacement and retirement are situated outcomes, not mandatory lifecycle steps.
Changing understanding does not by itself pause, delete, duplicate or reschedule a job. Use the real controller and exact selected authority for such effects, preserving in-flight work and a recovery route. Meta-Activity can connect original purpose, editable instructions and controller behavior; this competence retains the activity's continuing usefulness as its object.
Understand and improve an existing recurring activity's sources, method and connections when real work changes its usefulness. It may produce valuable knowledge, repeat unused results or encounter new possibilities.
Use this competence when an automation keeps running while its context, sources or served work have changed. Correct prompt execution does not establish continued usefulness. Consider the activity itself as the object and compose with Meta-Activity when recurring work needs revision.
Reach the activity's purpose, current configuration, sources, means and recipient. Start from an outcome or project change: repeated results, lost access, neglected opportunities, useful contributions or overlap. A trigger firing does not prove execution; silence does not prove uselessness. Do not add compulsory review to every run without a changed material relation.
Follow source, result and use. Distinguish information seen, prepared, preserved, received and actually used. A report available in a folder has not necessarily been read. Value may lie in a better question, prepared decision, avoided error or preserved possibility. When uptake is unknown, keep it unknown rather than assigning zero value.
Deepen the pertinent method when knowledge is missing. Repair the entry or recipient connection when knowledge exists but does not participate. Before combining overlapping activities, compare purpose, sources and consequences. A different cadence, clearer stopping condition or better source may suffice. Preserve original purpose and valid decisions; local optimization does not confer authority to change the mandate.
When reports seem saturated, consider whether the repeated question causes the limit. Seek a capability, relation, means or condition that changes what the next run can do. Preparing a recipient to use a result or making a source accessible may help. Develop the possibility supported by context without inventing activities to demonstrate improvement.
Correct the method within entrusted work. Changing a schedule, suspending or deleting an activity requires the actual mandate and controller. Compare configuration before and after, preserve concurrent changes and read back the saved effect. An instruction represents change; later execution and consequences show participation. Do not retire a useful activity merely because it produces no notifications.
Bring the recipient the smallest difference changing their work, with source, meaning and resumption condition where needed. Keep the reason for the method change in the activity guide. When experience changes how usefulness, saturation or overlap are understood, update this competence. A deferred possibility can retain its reopening condition without immediately creating another job.
The meta relation concerns the activity as a continuing capability: how it researches, produces and serves a recipient. Time triggers are only one means.
An autological return may change how this competence recognizes usefulness. An unread report may indicate a missing connection rather than useless research. Autonomous execution instead concerns actual means and mandate; it is distinct from this understanding.
Retain change when it helps the next use. This competence itself may be simplified or absorbed into a more suitable capability; useful work, not its own permanence, is its purpose.
Begin from available context and sources. Chat can exercise the method; persistence, tools and external effects depend on the recipient's means and mandate. Observe behavior and value in real work.
Read OPERATING_GUIDE.md as part of this method when forming the work. It carries the practical knowledge, decision relations and available means for this capability. The complete chat starter includes this knowledge and worked examples, so it remains usable without private sources. Preserve the public source identity and adapt through the recipient's actual means.
The meta relation concerns the activity as a continuing capability: how it searches, produces and serves a recipient. A time-based trigger is only one of its means.
An autological return can change how this competence recognizes usefulness. An unread report may expose a missing connection rather than useless research. Autonomy instead concerns executing actions with actual means and authorization; it is not the same as this understanding.
Competence, meta and autology: the conceptual guide ↗Retain a change when it helps the next use. This specialist competence can itself be simplified or absorbed by a better-suited capability: useful work matters more than preserving its current form.
Attach or paste START_CHAT_EN.txt, which contains the complete method, and add your context. The AI can work in the conversation's language. Retain the result and useful guidance if you want to resume in another chat.
Make the competence folder readable and have the agent read SKILL.md for the relevant work. Connect real sources and tools according to the environment's instructions. The kit does not install accounts, memory or recurring execution.
With an existing kernel, connect the method to the competence or guide already responsible for the work. Without one, apply the instructions directly and preserve useful knowledge in the project or a reusable note.
Read or copy the complete English starter and add your context. English is the kit’s primary language; Italian counterparts are included.
