Turn internal project learning into shareable knowledge
Identify the method, observation or capability that remains useful outside its original context.
When project experience could become a guide, method, resource or public case.
Competence · Products and communication · Public edition 0.3.2
A team discovers that its assistant read superseded documentation. The public guide explains the distinction between finding a source and establishing its version.
The key relationship. Separates reusable learning from private details and chooses a public form faithful to what was observed or built.
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 ↗A project produces knowledge while solving problems, recognizing limits and changing its method. Some of that knowledge can help people who know nothing about the original project.
This competence identifies the shareable relation and preserves the conditions that make it meaningful. Its public form may be an observation, a guide, a usable capability or a research question.
Start from a specific event or understanding: what happened, what was learned and which later choice could change. Identify value for an external recipient, such as understanding, use, inspection, collaboration or research. A code change or a new label is not by itself a reason to publish. An open question can still be useful when its status is clear.
Separate the useful mechanism from person-, client- and environment-specific details. Determine what survives in another case and which conditions must travel with it. Removing names is insufficient: a configuration-dependent problem does not become universal. A neutral example can explain the mechanism if it is identified as illustrative.
Distinguish observation, interpretation, implementation, exercise, repetition and external validation. A successful internal case is not a general performance result. Conversely, describe an established capability at the level its evidence supports. Keep decision-relevant uncertainty and scope visible in the main explanation.
Let the relation determine the form: a clarified failure can become a practical note, a repeatable method a guide, a capability a kit and an unresolved relation a research question. Use an existing public derivative when appropriate. Product truth and editorial expression remain distinct responsibilities; one event can inform several recipients.
When forming an operating resource, include the knowledge needed to perform and continue the work: accessible sources, decisions, conditions, tools and learning. A well-described principle is not the same as a received capability. Replace private dependencies with usable entries. A simple article does not need an unnecessary installation or package.
Protect personal data, credentials, private relationships and undisclosed strategy before a public effect. Preparation does not send or publish. After authorized sharing, use misunderstandings, critique and use cases to identify what should change: product, writing, distribution or the generalization method itself.
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 team discovers that its assistant read superseded documentation. The public guide explains the distinction between finding a source and establishing its version. Demonstration documents preserve the condition causing the failure without exposing project data.
A consulting project develops a useful way to compare requirements and deliveries. Share its criteria and a synthetic example. Exclude names, confidential amounts and internal comments while retaining the dependencies that make the comparison useful.
Unexpected behavior suggests a hypothesis. Present the observation, conditions and alternative explanations. The resource invites investigation without turning one experience into a law or a generalized experimental result.
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.
Separates reusable learning from private details and chooses a public form faithful to what was observed or built.
Understand what remains useful when private context is removed, what evidence supports it and why sharing helps the receiving public. Benefits can be comprehension, inspectability, trust, adoption, collaboration, research or useful business understanding; engagement is one possible consequence. A local observation, demonstrated method, implemented capability and open hypothesis can each be useful when their status remains clear. Do not invent maturity or demote a supported current capability to a mere possibility.
Remove private contacts, credentials, unpublished strategy, raw conversations, local account state and sensitive runtime details that are unnecessary to the relation. Keep the concrete mechanism and conditions making the lesson true. If the source has a canonical public derivative, let its native learning enter that owner before later explanation. A distinct lesson belonging to another domain returns there instead.
When the public destination is an independently usable competence or product, transfer usable method through its actual receiving entries and consumers. A principle added to a repository may leave the capability absent. An article alone need not load a compiler or packaging system. Choose guide, field note, research question, demo, product delta or another form from the contribution. Promotion readiness and actual publication are different states.
Public misunderstanding, critique, use, independent propagation and unchanged outcomes can teach different owners. Return a writing lesson to writing, a product lesson to the product and a generalization lesson to this method. Preserve claim scope and private/public lineage without forcing every observation into a content calendar.
Recognize which method, observation or capability retains value outside the context that produced it. Distinguish the reusable contribution from private details and form an account coherent with what was observed or built.
Use this competence when project experience could become a guide, method, resource or public case. Projects produce knowledge as they encounter problems, recognize limits and change methods. Preserve the shareable relation and the conditions giving it meaning. Its form may be an observation, guide, usable capability or research question.
Begin with a precise event or knowledge: what happened, what became understandable and which later choice might change. Consider the outside recipient's useful outcome: understanding, use, verification, collaboration or research. A technical change or new name is not sufficient reason to publish. An open question can have value when its state is clear and its source makes it understandable.
Separate the useful mechanism from details specific to a person, client or environment. Understand whether the relation retains meaning in another case and which conditions must accompany it. Removing names is insufficient: a problem depending on particular access or configuration does not become universal. Use a neutral example when it explains the same mechanism and identify it as illustrative.
Distinguish observation, interpretation, implementation, exercise, repetition and external validation. Do not turn one successful internal case into a general performance claim or weaken a supported capability into vague speculation. Make uncertainty, scope and revision clear where they affect understanding. A detail changing the conclusion belongs in the explanation, not a hidden note.
Let the relation determine form: a clarified error may become a practical note, a repeatable method a guide, a capability a kit or an unknown a research question. Reach an existing public owner for that capability before creating competing derivatives. The product owner retains capability truth; writing forms its expression. Several recipients may receive different contributions from one event.
For an operating resource, include the knowledge needed to perform and continue work: accessible sources, decisions, usage conditions, necessary tools and learning. A well-described principle is not the same as a received capability. Replace private dependencies with real entries and explain the method's contribution. A simple article does not require unnecessary installation or packaging.
Before a public effect, protect personal data, credentials, private relationships and strategies not selected for sharing. Preparation does not send or publish. After an authorized effect, use misunderstandings, criticism and usage cases to understand what should change: product, text, distribution or generalization. If the loss arose from selecting what was shareable, correct this competence itself.
The work has a meta relation when it takes another activity's learning as its object and forms a transferable capability. Not every observation requires a product.
An autological relation emerges when public feedback changes recognition and generalization of learning themselves. A guide that lost a decisive condition teaches this competence what to preserve next. That return is distinct from automatic publication.
Attribute the event, initial interpretation and later understanding. Public feedback may improve the resource without rewriting what the initial case actually showed.
Begin with actual context, sources, means and mandate. The method can operate in chat. Instructions make a capability usable; real work reveals its behavior and value.
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 work has a meta relation when it takes another activity's learning as its object and forms a transferable capability. Not every observation requires a new product.
An autological relation appears when public consequences change how learning is recognized and generalized. A guide that omitted a decisive condition teaches this competence what to preserve next time. That learning is distinct from automated publishing.
Competence, meta and autology: the conceptual guide ↗Keep the event, initial interpretation and later understanding attributable. Public feedback can improve the resource without rewriting what the original case actually showed.
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.
