Memory and skills
Skills
Repeatable procedures Gini follows — the bundled ones, the ones your team writes, and the ones it proposes after a job goes well.
A skill is a procedure Gini follows: how your company does a particular kind of job. The wiki holds facts; skills hold methods.
The difference matters when you're deciding where to put a correction. "Sam owns billing" is a fact. "Always check the CRM before drafting a customer email" is a skill.
Where they come from
Bundled. Gini ships with skills for the work most teams need: research, reporting, working with files and spreadsheets, handling attachments, common integrations. Every plan gets all of them. There's nothing to buy or turn on.
Yours. Written by your team, for how you do things.
Proposed. After a job goes well, Gini sometimes notices that the approach is worth repeating and proposes writing it down. You see the proposal, you read it, you accept or reject it. Nothing is learnt behind your back.
Writing one
Just describe the procedure:
@Gini when you write the weekly report: numbers first, then the one-line explanation, then what I should worry about. Never more than a page. Always compare to the same week last year, not last week.
@Gini for any customer escalation. Check HubSpot for the account owner, read the last 5 tickets, then draft a reply for them to send. Never send it yourself.
Gini turns that into a skill and shows you what it wrote. Correct it in the thread if it's off.
You can also write and edit skills at app.ginicomputer.com → Skills.
What makes a good one
A method, not a fact. If it's "who owns X" or "what X means", it belongs in the wiki.
Repeatable. If the steps change every time, you don't have a procedure, you have a job.
Worth the words. A skill that says "be helpful" does nothing. A skill that says "always compare to the same week last year" changes every report.
Say the sharp edges. The prohibitions are the valuable half: never send without review, never contact a customer without the owner cc'd, never use the spreadsheet, it's stale.
Reviewing what's there
app.ginicomputer.com → Skills lists everything Gini is following, including what it proposed and you accepted.
Worth a look when a job comes back in a shape you didn't expect. Often the cause is a skill written three months ago for a slightly different situation, still faithfully applied.
Edit or delete any of them.
Skills are workspace-wide
A skill you write applies to everyone's jobs, not just yours. That's usually what you want: it's how "we do it this way" becomes true. If a preference is really only yours, say so in the skill: "when Marcus asks for the report…".
Skills and approvals
A skill cannot widen what Gini may do. Writing "send the reminders automatically" into one does not remove the approval step, and it cannot reach the credential prompt or a connection's scope at all. Skills work the other way round: declaring that a step needs review adds a stop that then happens every time.
This is deliberate. If instructions could unlock actions, then anything that could write instructions could unlock actions.