Build agent skills around your context
Make a reusable skill reflect your sources, standards and review process, for individual work or a shared team workflow.
What is a contextual agent skill?
A contextual agent skill combines reusable task instructions with clear requirements for the sources, audience and constraints needed on each run. Prompeteer helps individuals and teams create these SKILL.md instructions from a task description, relevant files and selected Memory.
A proposal-review skill can keep the same review method while each engagement supplies its own approved product facts and current pricing. Identify those inputs in the skill instead of freezing a price list into the instructions. When a required source is missing, the workflow should ask for it.
Sources: Prompeteer product overview · Supported connections and Memory access
Give the skill enough context to make the right checks
Start with a small set of authoritative material. Name each document, the part relevant to this task and the output it should support. If two documents disagree, decide which is authoritative or return the conflict for review.
| Skill requirement | Proposal-review example |
|---|---|
| Trigger | Use when preparing or checking a proposal for an engagement. |
| Current sources | The approved product description and pricing document supplied for this customer. |
| Expected output | A claim-to-source review memo with exceptions and open questions. |
| Missing information | Pause the pricing check until the current document is supplied. |
| Review boundary | Return proposed edits; leave commercial approval with the responsible person. |
A reusable proposal-review skill
The skill should specify source checks the agent can perform with the access available to it.
Review a draft proposal against the pricing and product documents explicitly supplied for this engagement. Match claims to those sources, list exceptions and identify any unsupported commitments. If current pricing is missing, stop the pricing review and request the authoritative document. Produce a review memo, not an approved proposal. Never retrieve an external customer record without authorization.
Reuse your method as the work changes
An individual consultant can reuse the proposal-review method across engagements while supplying only the current client’s authorized documents. A researcher can keep a source-comparison method and replace the selected papers for each question. These are examples to adapt, not measured customer outcomes.
A team can agree the review criteria and name a skill owner who checks changes to the instructions. Record the current version, identify who reviews the output and supply fresh context for each project. Sharing a method does not mean every teammate should receive every source.
Check the context before you reuse the skill
Run the proposal example once with the required pricing source and once without it. In the first case, inspect whether each commercial claim points to the supplied document. In the second, verify that the skill requests the missing source instead of approving the price.
When aiming for contextual A+ skill creation, use Prompeteer Skill Score feedback to review the instructions and test the output separately. A+ is an internal quality target; it does not certify source accuracy, permissions or reliable performance in every agent.
Sources: Evaluate AI outputs with representative cases · Skill Score and Prompt Score: quality checks and limits
Check that the agent can read the context
A skill naming a source does not automatically connect to it. Use the supported file or Memory access path and verify that the current client receives the intended material. Keep customer data scoped to the task.
Common questions
Should a skill contain every company policy?
Usually it should state which policy is required and how to apply it. Keep large or changing reference material separate, with a clear version and access path.
Can individuals use contextual skills without a team?
Yes. A recurring personal work task can use the same method: define the trigger, supply the relevant context, inspect the generated instructions and test them in your agent.
Sources and review
Published by Prompeteer. See the people responsible for the product and contact the team with corrections. The linked workflow artifacts describe exactly what was checked; illustrative examples are not customer results.
Reviewed