Skill examples
See practical examples of task-specific methods that can be captured as reusable Skills in Giga.
Skills work best when they capture a specific repeatable method.
The examples below show the kinds of task instructions, standards, templates, and reference context that can make a useful Skill.
Account research
An Account Research Skill could teach Giga how your team researches a prospective customer.
It might define:
- which company facts to collect
- which sources or evidence to prioritize
- qualification criteria
- how to separate facts from inference
- the required output structure
- examples of a strong research summary
Useful with a Sales Agent
The Agent carries the broader sales research role.
Useful inside a Workflow
The Skill can provide the method for a research step when available.
Candidate screening
A Candidate Screening Skill could capture how your recruiting team evaluates a candidate against a role.
It might include:
- the criteria to assess
- how to distinguish evidence from assumptions
- the expected evaluation format
- interview or application evidence to reference
- examples of acceptable and weak evidence
The Skill stores the reusable screening method, while the specific candidate and role belong to the current task.
Customer update writing
A Customer Update Skill could define how your team prepares recurring customer-facing updates.
It might include:
- the preferred structure
- which facts should be confirmed before drafting
- terminology to use
- tone and formatting guidance
- what should be escalated for human review
A Chat can then supply the customer-specific facts for that one update.
Brand review
A Brand Review Skill could teach Giga how to review content against your company’s writing standards.
It might contain:
- brand voice rules
- words or phrases to avoid
- formatting preferences
- review criteria
- examples of acceptable and unacceptable copy
This works well as a reusable method because the same review standard can apply to many different pieces of content.
Document review
A Document Review Skill could define a repeatable review checklist.
For example:
- identify missing information
- flag contradictions
- check the document against the required standard
- separate required fixes from optional suggestions
- return findings in a consistent format
If the review becomes part of a larger ordered process, the Skill can sit alongside a Workflow.
Meeting summary
A Meeting Summary Skill could define what your company wants preserved from meeting notes.
It might ask Giga to identify:
- decisions
- owners
- open questions
- follow-up actions
- dates or deadlines explicitly stated
- useful durable context
The Skill defines the extraction method. The actual meeting notes remain task input.
Weekly reporting
A Weekly Reporting Skill could define how a recurring report should be prepared.
It might include:
- required sections
- how to summarize changes
- how to distinguish current state from historical detail
- metrics or evidence to include when available
- the expected final format
If the report should run automatically on a schedule, a Pulse handles the recurring timing while the Skill can carry the reporting method where the live configuration makes it available.
Support troubleshooting
A Support Troubleshooting Skill could capture a repeatable diagnostic method.
It might define:
- what evidence to collect first
- the order of diagnostic checks
- when to use a Connection
- what should be confirmed before taking an outward-facing action
- how to summarize the issue and next step
A Support Agent can carry the broader support role while the Skill stores this specific troubleshooting method.
Handoff preparation
A Handoff Skill could define how Giga turns active work into a concise handoff for another teammate.
It might require:
- current objective
- relevant background
- confirmed decisions
- unresolved questions
- immediate next steps
- links or references to the relevant work
This can be useful when moving work between people without copying the entire history.
What makes a strong Skill example?
Across these examples, the strongest Skills have the same basic properties:
| Strong Skill | Weak Skill |
|---|---|
| One recognizable task | Several unrelated jobs |
| Reusable method | One-off request |
| Clear standards | Vague goals |
| Useful supporting context | Large dump of unrelated information |
| Portable across relevant work | Tied unnecessarily to one specific Chat |
A Skill earns its place through reuse
If the instructions will only be used once, they can stay in the Chat. If the same method should guide future work, a Skill gives it a durable home.
From example to Skill
Spot a repeated method
Look for task instructions your team keeps explaining again.
Separate the method from the current task
Keep reusable rules in the Skill and task-specific facts in the Chat, Agent, Track, or Workflow.
Capture the method clearly
Write the instructions, standards, output expectations, and supporting references.
Share it where useful
Keep it private or share it into the Groups that should reuse it.
Image placeholder
Gallery-style visual showing several Skill cards: Account Research, Candidate Screening, Brand Review, Weekly Reporting, and Support Troubleshooting.