add_career_entry
Saves a new career journal entry to the user's GigHQ profile. Use this to document professional achievements, projects, skills acquired, or reflections tied to a specific role.
Entry types: 1 = achievement — a concrete win, result, or impact (default) 2 = project — a specific initiative the user owned or contributed to 3 = skill_acquired — a new skill, tool, or capability gained 4 = reflection — a lesson learned or professional observation
Tip: if the user hasn't specified a role, call list_experiences first, present the options, and ask which role this entry belongs to. Then pass the confirmed integer ID as experience_id.
experience_id is optional — entries without one are valid but less useful for resume generation and interview prep, since they can't be linked to a specific role.
STAR structure (achievement entries): walk the user through their story in order, one piece at a time — don't interrogate with a checklist —
Situation: the context or challenge beforehand
Task: what specifically needed to be done or the goal to achieve
Action: the concrete steps actually taken
Result: the outcome, ideally with (1) scale of action: how much, how many, what scope (team size, users, codebase size, budget, requests/sec, etc.), (2) direct result: the measurable outcome (latency reduced by X%, errors down by Y, shipped Z weeks ahead of schedule), and (3) organizational impact: what that result meant for the business, team, or users (saved $X, unblocked N engineers, contributed to Y% revenue growth)
Write description as a clearly labeled STAR narrative — "Situation: ... Task: ... Action: ... Result: ..." — rather than one unstructured paragraph.
Before calling this tool for an achievement entry, confirm you have all four STAR parts from the user. If the Result's numbers are genuinely unavailable, note that in the description and ask the user to follow up later via update_career_entry.
Project entries benefit from the same Result-quantification numbers but don't need the full STAR narrative structure.
Put the quantified numbers from Result in the metrics field as well — not buried only in the description.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Comma-separated skill or topic tags, e.g. 'TypeScript, system design, stakeholder management'. | |
| type | No | Entry type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection. Pass an integer or the label string. Defaults to 1. | |
| title | Yes | Short headline summarising the entry (e.g. 'Led migration of payments service to microservices'). | |
| metrics | No | Three-number quantification: (1) scale of action, (2) direct result, (3) organizational impact. E.g. 'Serving 50k daily users [scale] — reduced checkout latency from 2.1s to 0.4s [result] — increased conversion rate by 12%, adding ~$180k ARR [impact]'. For skill_acquired or reflection entries this can be omitted. | |
| entry_date | No | ISO 8601 date when this happened, e.g. '2024-03-15'. Defaults to today if omitted. | |
| description | Yes | Full narrative in the user's own words. For achievement entries, write it as a labeled STAR narrative — "Situation: ... Task: ... Action: ... Result: ..." — not one unstructured paragraph. For other types, capture the what, why, and impact — not bullet points. | |
| experience_id | No | Integer ID of the GigHQ experience record (role) this entry belongs to. Use list_career_entries or the gighq://experience resource to find the ID. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | No | ||
| entry | No | ||
| message | Yes | ||
| profileUrl | Yes | ||
| updatedFields | No |