get-started
Skill0 starsChanged 29 days agoMITView on GitHub
Onboard an investor, or import an existing investor's notes. Use for "get started", "set up my portfolio", "I'm new to this", "update my profile", "import my notes", or right after installing the plugin.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- blovett80/synero-mcptheir own version, first seen Nov 8, 2026
- Protoduct-AI/ledgie-plugintheir own version, first seen Nov 8, 2026
- chatmaxima-com/chatmaxima-skillstheir own version, first seen Nov 8, 2026
- pschlieker/getbacklanetheir own version, first seen Nov 8, 2026
- anotb/forward-deployedtheir own version, first seen Nov 8, 2026
- LeadMagic/leadmagic-claude-plugintheir own version, first seen Nov 3, 2026
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- glifxyz/glif-mcp-server★ 213same name
- different-ai/openwork-hub★ 35same name
- gomarble-ai/marketing-agent★ 15same name
- katalon-labs/true-skills★ 10same name
- PicsArt/gen-ai-skills★ 6same name
- Marky-Team/marky-skills★ 5same name
- multiples-hq/business-state-machine-mcp★ 2same name
- rams-design/rams-plugin★ 2same name
- anotb/forward-deployed★ 1same name
- asimokat/imzala-eklenti★ 1same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Ask which folder to keep their portfolio files in.
- Very specific: line 16
Write the first log_append with start_here: goal, current state in one line, next actions, decisions owed.
- Distinctive: line 17
Run the check skill for the first snapshot.
“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Get started
Plain language; explain each term (GTT, XIRR, SIP) once in a short parenthesis.
- Disclaimer first, and wait for an acknowledgement: "I provide analysis, not investment advice. I'm not SEBI-registered, I never suggest what to buy, and no order runs unless you approve the exact draft by clicking Yes in an inline question that lists every order."
- Ask which folder to keep their portfolio files in. Pass it as
--folderon the firstpccommand; it is remembered. - Ask in one friendly message: goal and years to it; a 20% fall in a month: sell, hold or buy more (conservative / balanced / aggressive); monthly investment and idle lump sum; brokers (Zerodha and Kotak Neo connect live; IBKR via its connector; any other broker by CSV import); where the emergency cash buffer is kept (broker or bank).
- Save with
profile_update, one path at a time:investor.*,brokers.kotak.enabledandbrokers.kotak.ucc,cash.buffer_location,allocation.targetsif they have them,deployment_planif they have a staged plan. For the plan, savecorpus_source(the name of the holding that is the war chest, e.g. "ARBITRAGE") rather than a fixedcorpus_inr, so the corpus is read live, and setstages[i].done_atfor stages already deployed. Confirm each in a short summary. - Verdicts: as the investor states a stance on a holding, save
verdicts.<SYMBOL>={stance, reason, exit_level?}. Stances: hold, add, hold_no_add, reduce, exit, or trade (a short-term position with its own stop and target). - Existing notes ("import my notes"): read their files, extract rules only (thresholds, GTT policy, buffer location, allocation targets, staged plan, verdicts with reasons). Show each proposed item and save it only after the investor confirms it. Never import snapshot numbers (quantities, prices, P&L, dated totals) as rules.
- Write the first
log_appendwithstart_here: goal, current state in one line, next actions, decisions owed. - Run the check skill for the first snapshot. Explain it in 3-4 sentences and the one most important next action.
- Offer a routine: "check" each morning, "risk" on Fridays, "gtt" after any buy or sale. A scheduled weekday check works, but Indian brokers expire logins daily, so an unattended run gives macro plus the last snapshot.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

