Skills

Most response teams now have someone using ChatGPT, Claude, or Copilot to help with tenders. The skills they have developed, the prompts that produce a good draft, the templates that hold up under review, the methodology that surfaces the right evidence, all of it lives in individual chat histories. None of it is centralised across the business. None of it is captured. When the person leaves or moves teams, the skill leaves with them.

Skills is the answer to that problem. A skill is a detailed, structured prompt that controls how Tendl behaves in a specific workflow. Writing the strategic plan. Drafting a delivery methodology section. Generating a compliance response in a particular tone. Reviewing for legal risk. Each skill is configurable, version-controlled, and shared across the team.

When someone improves a skill, the improvement is available to the whole team immediately. When the team agrees a particular methodology should be applied consistently, the skill enforces it. When the strategic plan should follow a specific structure, the skill carries that structure into every plan.

This is the layer that turns AI assistance from a private hack into a team capability. The knowledge compounds across the business instead of staying trapped in individual accounts.