# Shared skills for working with AI

> Choose a skill and your role for practical guidance, everyday AI-assisted work examples and a small exercise to help you improve.

Source: https://helmframework.com/competencies
Updated: 2026-10-22
License: https://creativecommons.org/licenses/by/4.0/

[HELM 1.0.1](https://helmframework.com/changelog) · Updated 2026-10-22

HELM suggests five competencies—skills and behaviors you can practice—to help you make good choices, work with others and take responsibility for results.

Choose a skill you want to develop, then your role. Each guide gives you practical steps, an example and a small exercise. These ideas build on [HELM’s six principles](https://helmframework.com/foundation).

## Five skills to practice

1.  ### 01 Judgment
    
    Choose a useful outcome and the simplest approach. Decide what to delegate and when a person needs to step in.
    
    [Practice Judgment](https://helmframework.com/competencies#content-judgment)
    
2.  ### 02 Communication
    
    Give people and agents the goal, context, constraints and a clear idea of a good result.
    
    [Practice Communication](https://helmframework.com/competencies#content-communication)
    
3.  ### 03 Evaluation
    
    Check AI-assisted work against facts and requirements. Make uncertainty visible.
    
    [Practice Evaluation](https://helmframework.com/competencies#content-evaluation)
    
4.  ### 04 Ownership
    
    Take responsibility for the work you use or share. Respect decision boundaries and follow through on problems.
    
    [Practice Ownership](https://helmframework.com/competencies#content-ownership)
    
5.  ### 05 Learning
    
    Use feedback to improve, practice the skills you need to check agent work, and share useful lessons.
    
    [Practice Learning](https://helmframework.com/competencies#content-learning)
    

## Build a skill in your role

Pick one competency to work on. The expectations stay the same across roles; the guidance helps you put them into practice in your own work. The examples are illustrative situations to learn from and adapt.

In my role or team

Content · Practice guide

### Preparing an email campaign for a new service

#### Judgment

[Link to this guide](https://helmframework.com/competencies#content-judgment)

##### How to build it

1.  Start with the audience’s question and the action you want to help them take. Decide whether an existing page or email already answers it.
2.  Compare updating that material with creating something new. Choose the smallest useful asset before asking an agent for drafts.

##### Illustrative example

The marketer chooses one focused email answering a common customer question, instead of generating a large campaign before knowing what the audience needs.

##### Try it on your next task

For your next brief, write the audience’s question, two possible approaches and why you chose one. Ask a colleague what might change that choice.

**Check yourself:** Can you explain your choice, the trade-off and what would make you reconsider?

#### Communication

[Link to this guide](https://helmframework.com/competencies#content-communication)

##### How to build it

1.  Give the agent the audience, offer, approved sources, tone and desired action. Separate confirmed product facts from ideas to explore.
2.  Give the reviewer the same brief and point out unresolved claims or assumptions. Keep changes to the brief visible to both.

##### Illustrative example

They give the agent the audience, offer, approved product facts, tone and desired action: “Encourage existing customers to book a walkthrough.”

##### Try it on your next task

Rewrite one vague content request into a brief with a goal, sources, constraints and an example of the tone you want.

**Check yourself:** Could someone act on your brief without guessing the goal or constraints?

#### Evaluation

[Link to this guide](https://helmframework.com/competencies#content-evaluation)

##### How to build it

1.  Trace factual claims, prices and promises to current approved sources. Qualify or remove statements the sources cannot support.
2.  Read the draft as the intended audience: is the offer clear, and does the linked page deliver what the message promises?

##### Illustrative example

They catch an AI-generated claim that the service “cuts costs by 50%.” They check the available evidence and replace it with an accurate description.

##### Try it on your next task

Pick the three strongest claims in an AI draft. Record the supporting source for each and revise any claim that overstates it.

**Check yourself:** Can you show what you checked and what remains uncertain?

#### Ownership

[Link to this guide](https://helmframework.com/competencies#content-ownership)

##### How to build it

1.  Agree who checks product facts and who approves publication. Confirm those checks before sending or scheduling content.
2.  If something is wrong after publication, correct it, inform the people affected and check that downstream copies are updated.

##### Illustrative example

They notice the published email contains an outdated price. They coordinate the correction, inform the sales team and address affected customer enquiries.

##### Try it on your next task

For one upcoming asset, agree who approves its claims and who will handle a correction. Follow an open correction through to completion.

**Check yourself:** Do the people affected know who will decide and what happens next?

#### Learning

[Link to this guide](https://helmframework.com/competencies#content-learning)

##### How to build it

1.  Compare the intended audience action with what happened. Use reader feedback as well as clicks to identify a possible improvement.
2.  Change one part of the next comparable asset and review the result. Record other differences before attributing an improvement to your change.

##### Illustrative example

The campaign gets clicks but few bookings. They review the email and landing page, identify a possible mismatch, and test a clearer promise next time.

##### Try it on your next task

Take one confusing message from a recent campaign, test a clearer version with a reader and share what you changed and learned.

**Check yourself:** What changed in your next attempt, and what did you learn from trying it?

Engineering · Practice guide

### Adding a report-download feature with a coding agent

#### Judgment

[Link to this guide](https://helmframework.com/competencies#engineering-judgment)

##### How to build it

1.  Define the user-visible result and compare the smallest viable change with a larger redesign. Consider effort, failure consequences and how you will check the result.
2.  Separate predictable implementation from decisions about access, data changes or release risk. Give the agent a bounded task and name the human checks.

##### Illustrative example

The engineer delegates routine file-formatting code to the agent and gives closer human attention to which records each customer may access.

##### Try it on your next task

Split your next change into work to delegate and decisions or checks you will own. Explain one boundary to a reviewer before implementation.

**Check yourself:** Can you explain your choice, the trade-off and what would make you reconsider?

#### Communication

[Link to this guide](https://helmframework.com/competencies#engineering-communication)

##### How to build it

1.  Provide expected behavior, relevant project context, constraints and concrete input/output examples. Include important failure cases, such as an empty report or a wrong-account request.
2.  Share the same expectations with the reviewer. Explain discoveries and assumptions that changed during implementation.

##### Illustrative example

They specify the required columns, filters, access rules and expected behavior for empty results, with an example of the finished report.

##### Try it on your next task

Improve one task description with a normal case, a failure case and an example of a correct result before asking the agent to implement it.

**Check yourself:** Could someone act on your brief without guessing the goal or constraints?

#### Evaluation

[Link to this guide](https://helmframework.com/competencies#engineering-evaluation)

##### How to build it

1.  Check the change against the intended behavior, not just the tests the agent wrote. Review the code and test important boundaries independently.
2.  Try a plausible failure case and explain what your checks cover. Ask for specialist help where you cannot judge the result confidently.

##### Illustrative example

The generated code passes its tests, but the engineer checks with two customer accounts and discovers that the export includes another customer’s records.

##### Try it on your next task

Before reading the agent’s tests, predict one important way the change could fail. Add or run a check that would expose that failure.

**Check yourself:** Can you show what you checked and what remains uncertain?

#### Ownership

[Link to this guide](https://helmframework.com/competencies#engineering-ownership)

##### How to build it

1.  Know which changes you can approve and which need another decision owner. Make remaining risks and release conditions explicit.
2.  Follow the change into use: verify the released behavior, respond to problems and confirm who will handle any remaining work.

##### Illustrative example

They confirm the access issue is fixed, involve the appropriate reviewer and verify that the released feature behaves as intended.

##### Try it on your next task

For your next release, record how you will verify the result and who will respond if it fails. Follow up after release.

**Check yourself:** Do the people affected know who will decide and what happens next?

#### Learning

[Link to this guide](https://helmframework.com/competencies#engineering-learning)

##### How to build it

1.  When an agent-assisted change fails, understand the cause before accepting another patch. Explain why the fix addresses the problem.
2.  Add a useful test or example that catches the failure next time, then share the lesson with the team.

##### Illustrative example

A customer name containing a comma breaks the exported file. They add a test that catches this problem and include the edge case in future task briefs.

##### Try it on your next task

Choose one recent defect. Explain its cause in your own words and demonstrate a check that fails before the fix and passes after it.

**Check yourself:** What changed in your next attempt, and what did you learn from trying it?

Sales · Practice guide

### Drafting a proposal after a discovery call

#### Judgment

[Link to this guide](https://helmframework.com/competencies#sales-judgment)

##### How to build it

1.  Clarify the customer’s problem, essential requirements and constraints before selecting an offer. Separate what they said from assumptions in the AI summary.
2.  Compare suitable options, including a smaller package or acknowledging a poor fit. Base the recommendation on the customer’s need and what can actually be delivered.

##### Illustrative example

The salesperson recommends a smaller package that meets the customer’s actual need, even though the agent’s draft promotes the most expensive option.

##### Try it on your next task

Compare two feasible offers for one opportunity. Explain why one fits better and what new information would change your recommendation.

**Check yourself:** Can you explain your choice, the trade-off and what would make you reconsider?

#### Communication

[Link to this guide](https://helmframework.com/competencies#sales-communication)

##### How to build it

1.  Give the agent the customer’s stated needs, decision criteria and approved commercial information. Mark unanswered questions clearly.
2.  Keep confirmed commitments separate from suggestions in the proposal and handover. Make sure the customer and delivery team receive the same understanding.

##### Illustrative example

They provide the customer’s problem, budget, decision criteria, approved pricing and unresolved questions before asking the agent to draft the proposal.

##### Try it on your next task

Turn one call into a short brief: customer need, constraints, confirmed facts and open questions. Check the brief before generating a proposal.

**Check yourself:** Could someone act on your brief without guessing the goal or constraints?

#### Evaluation

[Link to this guide](https://helmframework.com/competencies#sales-evaluation)

##### How to build it

1.  Check scope, pricing, integrations and dates against current product information and delivery confirmation.
2.  Check whether the proposal addresses the customer’s actual decision criteria. Correct attractive wording that implies an unsupported promise.

##### Illustrative example

They compare the draft with call notes and product information, catching an integration and delivery date that the company has never confirmed.

##### Try it on your next task

Highlight every commitment in a draft proposal. For each, identify the supporting source or person who must confirm it before sending.

**Check yourself:** Can you show what you checked and what remains uncertain?

#### Ownership

[Link to this guide](https://helmframework.com/competencies#sales-ownership)

##### How to build it

1.  Confirm commitments with the people responsible for delivering them before promising them to a customer.
2.  Record what was agreed, hand over unresolved questions and follow up on commitments you made. Correct a misunderstanding promptly.

##### Illustrative example

They confirm commitments with the delivery owner, explain remaining uncertainties to the prospect, and record what was agreed for the account handover.

##### Try it on your next task

For one deal handover, distinguish agreed commitments from pending requests and confirm the receiving owner understands both.

**Check yourself:** Do the people affected know who will decide and what happens next?

#### Learning

[Link to this guide](https://helmframework.com/competencies#sales-learning)

##### How to build it

1.  Review a won or lost opportunity using customer feedback and call notes. Separate a confirmed reason from your own explanation.
2.  Try one improvement to discovery or qualification on the next comparable opportunity and share the result.

##### Illustrative example

After losing the deal, they learn that an essential requirement surfaced too late. They add an earlier discovery question and share the lesson with colleagues.

##### Try it on your next task

Identify one question you asked too late in a recent deal. Ask it earlier on the next relevant call and note whether it changes the discussion.

**Check yourself:** What changed in your next attempt, and what did you learn from trying it?

Account Management · Practice guide

### Preparing a customer review before renewal

#### Judgment

[Link to this guide](https://helmframework.com/competencies#account-management-judgment)

##### How to build it

1.  Start with the customer’s desired outcome, unfinished commitments and current blockers. Check whether the AI summary reflects those priorities.
2.  Compare resolving the blocker, supporting adoption or proposing an upgrade. Choose the next action using evidence of customer value.

##### Illustrative example

The account manager prioritizes resolving an adoption blocker before proposing an upgrade, because the customer is struggling to get value from the current service.

##### Try it on your next task

Before one account review, choose the most useful next action. Write the evidence behind it and one signal that would make you reconsider.

**Check yourself:** Can you explain your choice, the trade-off and what would make you reconsider?

#### Communication

[Link to this guide](https://helmframework.com/competencies#account-management-communication)

##### How to build it

1.  Bring together the customer’s goals, usage, support history and previous commitments. Distinguish observed facts, customer reports and assumptions.
2.  Make owners, next actions and unresolved questions clear in both the agent brief and the customer conversation.

##### Illustrative example

They give the agent the customer’s goals, previous commitments, support history and usage data, clearly identifying facts that still need confirmation.

##### Try it on your next task

Prepare a five-line account brief: goal, progress, blocker, next commitment and open question. Confirm uncertain facts with the relevant person.

**Check yourself:** Could someone act on your brief without guessing the goal or constraints?

#### Evaluation

[Link to this guide](https://helmframework.com/competencies#account-management-evaluation)

##### How to build it

1.  Check the AI summary against usage records, support history and the customer’s own account of progress.
2.  Look beyond activity measures such as logins. Ask whether the work that matters to the customer is getting completed.

##### Illustrative example

The AI summary describes the account as healthy because logins increased. They check whether the customer’s important workflows are actually being completed.

##### Try it on your next task

Take one AI-generated account-health statement. Find evidence that supports or challenges it and prepare a question to resolve what is unclear.

**Check yourself:** Can you show what you checked and what remains uncertain?

#### Ownership

[Link to this guide](https://helmframework.com/competencies#account-management-ownership)

##### How to build it

1.  Turn commitments into clear actions with an agreed owner and check-back date. Confirm the responsible team can deliver before giving a date to the customer.
2.  Communicate delays early, agree a recovery action and check with the customer that the issue is actually resolved.

##### Illustrative example

They acknowledge a missed commitment, agree a recovery action with the responsible team, and follow up with the customer until it is resolved.

##### Try it on your next task

Pick one outstanding customer commitment. Confirm the owner, next action and follow-up date, then check with the customer that it was resolved.

**Check yourself:** Do the people affected know who will decide and what happens next?

#### Learning

[Link to this guide](https://helmframework.com/competencies#account-management-learning)

##### How to build it

1.  Look for recurring questions or blockers across account reviews. Ask customers and delivery colleagues what made the work difficult.
2.  Improve one onboarding or handover step, try it on the next relevant account and check whether the confusion is reduced.

##### Illustrative example

Several accounts encounter the same onboarding confusion. They improve the handover checklist, try it with the next account and check whether it helps.

##### Try it on your next task

Turn one repeated customer question into a clearer handover instruction. Try it with the next account and share the feedback.

**Check yourself:** What changed in your next attempt, and what did you learn from trying it?

## Choose one thing to practice

Pick a recent piece of AI-assisted work and discuss:

1.  Which of these behaviors helped, or would have helped?
2.  What example from the work supports that view?
3.  What will you practice on the next similar task?

Consider the opportunity and support people had. If there is not enough evidence, say so. Use this for learning and feedback; a formal evaluation method is still being developed.
