Traveller RPG skills become easier to roleplay when every check begins with a goal and a plausible action instead of a skill name alone.
Compare two versions of the same moment:
“I roll Electronics.”
“I compare the sensor logs with the maintenance record and look for the component that began drifting before the array failed.”
The second version gives the table an intended result, an observable approach, a reason the character’s expertise matters, and useful material for interpreting the roll.
The player does not need to know how a starship sensor array works. The player only needs to say what the character wants and offer a plausible approach. The character’s skill supplies the professional knowledge.
This guide shows players how to describe Traveller RPG skills in play and gives Referees a practical way to decide when to roll, establish stakes, and turn the result into the next decision. For a broader beginner learning path, visit the Traveller Player Guide.
A Skill Is Training, Not an Action Button
“I use Engineer,” “Can I roll Persuade?” and “I make a Recon check” identify possible mechanics, but they do not tell the table what the character is doing.
A skill describes trained capability. The fiction describes the action. Start with the outcome the character wants and the method they use to pursue it, then identify the skill that fits.
Compare:
“I roll Broker.”
with:
“I point out that the cargo is already costing the seller storage fees and offer to close the deal now if they reduce the price.”
The second statement establishes leverage, urgency, and a concrete proposal. It helps the Referee decide whether Broker applies, whether a roll is necessary, and what a poor result might cost.
Players do not need to conceal the rules. “I want to calm the dockmaster by explaining the quarantine risk. Would Persuade apply?” is a useful declaration because it includes intent, approach, and a suggested mechanic without treating the skill as a button.
Training should also affect what a character notices and understands. An engineer recognizes warning signs in a power system. A broker notices suspicious fees or false urgency. A medic identifies which injury is immediately dangerous. Recon reveals sightlines, concealment, surveillance positions, or behavior that does not fit the surroundings.
The skill does not replace the action. It explains why the character can attempt the action professionally.
Start With Intent and Approach
A useful player statement follows a simple pattern:
“I want to achieve this result, so I take this approach.”
For example:
- “I want to identify the cause of the drive failure, so I compare the maintenance record with the current diagnostic readings.”
- “I want the port officer to let us leave, so I explain the medical emergency and offer to transmit our logs.”
- “I want to know whether the patron is hiding something, so I ask about the payment schedule again and watch how they react.”
- “I want to follow the courier without being noticed, so I use crowds and service corridors instead of staying directly behind them.”
Once the table knows the goal and method, the Referee can decide whether a roll is required, which skill fits, whether another skill could create a different solution, and what the outcome will change.
Use the Detail Level That Helps the Scene
Intent only: “I try to stabilize the passenger.” This can be enough when the player is new, the scene is moving quickly, or the details are not important.
Plausible approach: “I stop the bleeding and check whether the suit is hiding another injury.” This is the useful default because it distinguishes the action without demanding specialist knowledge.
Detailed professional description: “I isolate the damaged suit section, stabilize the blood loss, and check for decompression trauma before moving them.” This can add flavor when a player enjoys technical detail, but it should never be required.
The Referee can provide expertise the player does not possess: “With Medic, you know moving the passenger now could worsen a spinal injury. Are you stabilizing them here, or risking the move before security arrives?” The character receives a professional judgment, while the player keeps control of the decision.
The Traveller Skill Roleplay Loop
Use this six-step loop to turn almost any Traveller RPG skill check into a visible action with a meaningful outcome.
- Intent: Identify what the character wants. They may be trying to diagnose a fault, enter a restricted area, stabilize a patient, avoid surveillance, locate a buyer, or reach orbit before interception.
- Approach: Describe what the character does. They might inspect logs, cite a regulation, compare two stories, stop the bleeding first, contact a former associate, or use a planet to mask departure.
- Expertise: Show what training contributes. Engineer recognizes a failure chain. Advocate identifies jurisdiction. Recon notices a surveillance position. Broker identifies who controls the deal.
- Risk: Establish why the outcome is uncertain. Time pressure, incomplete information, poor tools, danger, opposition, legal exposure, unfamiliar technology, or conflicting priorities can make a check matter.
- Result: State what the character accomplishes, discovers, prevents, exposes, damages, or worsens. Avoid ending with only “You succeed” or “Nothing happens.”
- Consequence: Present the new decision, cost, danger, opportunity, or obligation created by the result.
The loop is not another procedure to recite before every roll. It is a way to notice what information the scene needs. A single clear sentence may establish several steps at once.
Give Trained Characters Useful Information
Trained characters should often receive professionally obvious information without rolling. The following examples show how expertise can shape the scene before uncertainty, pressure, or opposition requires a check.
| Skill | Professionally Obvious Information |
|---|---|
| Engineer | The vibration comes from the power plant rather than the manoeuvre drive. |
| Broker | The quoted price contains a suspicious handling fee. |
| Advocate | The official is citing the wrong jurisdiction. |
| Recon | The crowd is avoiding one apparently ordinary passenger. |
| Medic | The symptoms do not match the reported accident. |
| Astrogation | The plotted route leaves almost no margin for error. |
| Mechanic | The damaged component was replaced recently. |
| Streetwise | The contact chose the meeting place for its exits and weak surveillance. |
Use this distinction to separate professional awareness from uncertain action. A roll should resolve danger, pressure, opposition, incomplete information, or meaningful cost—not whether a trained character understands the basics of their profession.
Let Different Skills Create Different Solutions
One problem may support several valid approaches. Those approaches should not produce an identical scene with a different modifier. Consider a crew that needs access to a sealed cargo bay.
| Approach | Possible Skill | Likely Consequence |
|---|---|---|
| Convince the port officer there is an emergency | Persuade | The officer may demand proof or become personally involved. |
| Cite an inspection regulation | Advocate | The action creates a formal legal record. |
| Change the cargo authorization | Admin or Electronics | Discovery may produce fraud or computer-crime charges. |
| Find a worker with legitimate access | Streetwise | The worker wants payment, protection, or a favor. |
| Bypass the electronic lock | Electronics | The security system may record the intrusion. |
| Enter through a service panel | Mechanic | The route may cause damage, delay, or exposure. |
The chosen skill should influence who becomes involved, what evidence remains, which risk the crew accepts, and what future problems become possible. Skill selection then becomes a fictional choice rather than a search for the highest number.
Make Success Look Competent
A successful check should normally make the character look trained. The dice resolve uncertainty; they do not erase the experience already established on the character sheet.
- An engineer isolates the unstable relay, reroutes power, and prevents the fault from reaching another system.
- A broker recognizes that the supposed owner is an intermediary and negotiates with the actual decision-maker.
- A scout notices the surveillance team before the ambush is fully established.
- A medic identifies a hidden internal injury before the patient’s condition collapses.
After establishing the result, the Referee can invite the player to describe the finish: “You know what must be done. What does it look like when your character takes control?”
This invitation is optional. Some players enjoy narrating the final action; others prefer the Referee to describe it. Either style works when the outcome remains clear.
Let Failure Preserve Expertise
A failed check does not have to mean that a trained engineer forgets engineering, a medic misses an obvious injury, or an advocate forgets the law.
Failure can mean the task takes too long, the correct tools are unavailable, the information is incomplete, the opposition anticipated the approach, the situation changes before completion, or the only workable solution creates a difficult cost.
Use the following examples to turn a poor result into a consequence that respects expertise while still putting pressure on the crew.
| Skill Check | Competence-Preserving Failure |
|---|---|
| Engineer | The fault is identified, but repairing it requires shutting down another vital system. |
| Medic | The patient can be stabilized only by using the crew’s last critical treatment resource. |
| Advocate | The argument is valid, but the official refers it to a superior and creates a delay. |
| Recon | The ambush is detected, but the easiest escape route is already blocked. |
| Broker | A buyer is found, but they exploit the crew’s urgency and demand a steep concession. |
| Astrogation | A safe route exists, but taking it costs time the crew may not have. |
| Electronics | The system can be bypassed, but the intrusion will leave evidence. |
| Persuade | The target agrees only after demanding a promise, favor, or guarantee. |
Competence-preserving failure does not protect characters from consequences, and it does not require every failed roll to become success with a cost. The action may genuinely fail. The important point is that the reason should arise from pressure, opposition, tools, timing, or the situation rather than making a professional arbitrarily foolish.
Ask Questions That Build the Fiction
When a player names only a skill, the Referee does not need to reject the declaration or demand a technical speech. One or two supportive questions can reveal the missing intent or approach:
- What are you trying to accomplish?
- How are you doing it?
- What are you using?
- Are you prioritizing speed, safety, secrecy, or certainty?
- What will happen if this takes too long?
- What would your character’s training reveal immediately?
Do not turn these prompts into an interrogation. Ask only what the scene needs.
Players can also request expert context: “What would my character know about this?” “Does anything look wrong to someone with Engineer?” “Which option would leave the least evidence?” The Referee supplies information the character could reasonably possess, and the player decides what to do with it.
This division preserves player agency. The Referee describes professional context and consequences; the player chooses the character’s priorities, methods, and risks.
Decide When a Roll Matters
Not every skilled action needs a check. A trained engineer performing routine maintenance with suitable tools and enough time should not roll merely to prove they know their job.
Do not roll when:
- The result is already certain.
- The action is routine for the character.
- Failure would not change anything important.
- Nothing is pressuring or opposing the character.
- The table needs the information in order to make a meaningful decision.
Roll when:
- The outcome is uncertain.
- Failure changes the situation.
- Time, danger, opposition, or resources matter.
- Different outcomes create different decisions.
Use the dice when uncertainty produces a meaningful difference in what happens next.
Establish the Stakes Before the Roll
Where practical, tell the player the broad risk before the dice are rolled. The Referee does not need to reveal every hidden consequence, but the player should understand the kind of danger being accepted.
“You can bypass the lock with Electronics. On a poor result, you may leave evidence in the security system.”
The player can now accept the risk, change the approach, seek assistance, spend more time, find better tools, choose another skill, or abandon the attempt. This makes the roll a decision instead of a surprise punishment.
Use Teamwork and Career History
Assistance should appear as an observable contribution rather than existing only as a modifier.
- The engineer diagnoses the fault while the mechanic exposes the damaged assembly.
- The medic treats the patient while another character monitors vital signs.
- The broker negotiates while the steward watches the room and reads reactions.
- The advocate builds the legal argument while the administrator locates the relevant records.
This approach gives more players a meaningful role in tasks that might otherwise become one-character scenes.
Career history can also color how a skill appears. A former naval engineer may begin with procedure and redundancy. A merchant engineer may focus on economical repairs and keeping the ship moving. A scout engineer may expect field conditions and improvise with limited support.
These are flavors, not restrictions. Career history can suggest habits, vocabulary, contacts, equipment, and methods without requiring the player to perform an autobiography or forbidding another approach.
Worked Example: Losing Thrust Near a Hostile Port
Situation
The crew’s ship begins losing thrust while approaching a hostile port. The port is demanding compliance with an assigned docking corridor.
Intent
The engineer wants to restore enough thrust to keep the crew from being forced into the port’s control.
Approach
The engineer compares current power flow with the last maintenance cycle and isolates systems one at a time.
What Expertise Reveals
Engineer tells the character that the symptoms resemble a power-conditioning failure rather than physical engine damage.
Why a Roll Is Needed
The ship is still moving, the port is increasing pressure, and shutting down the wrong system could remove manoeuvre control entirely. Time, danger, and incomplete control make the outcome uncertain.
Success
The engineer reroutes power through a secondary system and restores limited thrust. The crew can choose another destination, but the temporary bypass will fail after another major manoeuvre.
Failure
The engineer identifies the fault but cannot bypass it safely while the drive remains active. The crew must choose between shutting down thrust for a proper repair or entering the hostile port under reduced control.
The New Decision
Both results preserve the engineer’s competence and change the scene. The dice answer a specific question, and the answer gives the crew a new choice rather than stopping play.
Player Quick Procedure
- State what you want.
- Describe a plausible approach.
- Suggest a skill when helpful.
- Ask what your training tells you.
- Confirm what changed after the roll.
- Describe the competent action when invited.
- Respond to the new consequence or opportunity.
This procedure is a support tool, not a performance requirement. One clear sentence may handle the first three steps.
Referee Quick Procedure
- Clarify the character’s intent.
- Clarify the approach only as much as needed.
- Provide professionally obvious information.
- Decide whether uncertainty matters.
- Establish the broad stakes.
- Resolve the check using the rules and circumstances of the campaign.
- Describe a concrete result.
- Present the next decision.
For broader advice on playable situations, consequences, and campaign decisions, continue with the Traveller Referee Workshop.
Make the Dice Answer a Fictional Question
Before rolling, the table should be able to complete this sentence:
“We are rolling to find out whether…”
- …the engineer isolates the fault before the patrol ship arrives.
- …the advocate prevents the inspection from becoming an arrest.
- …the medic stabilizes the passenger without exhausting the crew’s remaining treatment resources.
- …the broker closes the deal before a rival buyer intervenes.
A clear question connects the rules to the fiction. The character’s training shapes the attempt, the risk makes the roll necessary, and the result changes what the crew must decide next.
Frequently Asked Questions
Do players need real-world technical knowledge?
No. A player needs a goal and a plausible approach, not professional expertise. The Referee can supply relevant information that the trained character would understand.
Can players suggest which skill applies?
Yes. Naming a likely skill can make play faster when the player also explains the intended outcome and approach. The Referee can accept the suggestion, identify another fit, allow several routes, or decide that no roll is needed.
Should every use of a skill require a roll?
No. Roll when uncertainty, pressure, opposition, danger, time, or meaningful cost can change what happens next. Routine professional activity can often succeed without a check.
How can failure preserve character competence?
Let failure arise from the situation: limited time, poor tools, incomplete information, strong opposition, exposure, or a difficult tradeoff. The task may still fail, but the character does not need to become inexplicably incompetent.
Can different skills solve the same problem?
Often, yes. Different skills should create different methods, risks, evidence, contacts, and consequences. The choice matters because it changes the fiction, not merely the number on the roll.
Does this method replace Traveller task rules?
No. It helps the table frame and interpret checks. Use the rules of the Traveller edition and campaign you are playing to resolve the task itself.
Use Traveller RPG Skills With Confidence
Start by saying what the character wants and how they act. Let training reveal professional context, use the dice only when uncertainty matters, and turn every result into a concrete change or decision.
Players do not need to perform specialist knowledge, and Referees do not need to demand elaborate narration. Intent, approach, expertise, risk, result, and consequence are enough to make Traveller RPG skills feel like part of the world rather than buttons on a character sheet.
Get More Traveller Character and Skill Guides
Continue building confident Travellers with practical guidance for character creation, careers, skills, and play at the table.
