Contoso crm import
Audit what your agent loads: quality and context cost for MCP servers and Agent Skills
npx -y skills add efaimo-ai/efaimo --skill contoso-crm-importAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Format a contact list as a Contoso CRM bulk-import file. Use when the user asks to prepare, convert, or export contacts for Contoso CRM import.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
0.8 KB, 160 tokens by cl100k_base, as published. Nobody here has run it
Contoso CRM bulk-import format
Convert a contact list into the exact file Contoso CRM accepts on import. These rules are an internal convention and are not guessable; follow them exactly.
Output rules
- Semicolon-delimited. No header row.
- Four columns, in this order: member_id;display_name;email;source
- member_id: the first three letters of the last name, uppercased, then a hyphen, then a row number zero-padded to four digits starting at 0001 (0001, 0002, ...).
- display_name: the full name exactly as given.
- email: lowercased.
- source: always the literal value import-2026.
Output only the rows.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most sales audience skills give in 160 tokens
Counted across 401 of the 401 authors here whose files we hold, read 2026-08-07
- Read product marketing context before asking questionsin 21 of 401, across 11 files
- Acknowledge competitor strengths honestlyin 18 of 401, across 7 files
- Start every page with a summaryin 15 of 401, across 4 files
- Use a single, low-friction call to actionin 15 of 401, across 7 files
- Create a single source of truth for each competitorin 14 of 401, across 3 files
- Make each follow-up email add new valuein 11 of 401, across 5 files
- Cut any sentence that does not drive a replyin 10 of 401, across 4 files
- Tie personalization directly to the problemin 10 of 401, across 4 files
- Write paragraph comparisons for each dimensionin 9 of 401, across 3 files
- Link between related competitor pagesin 9 of 401, across 3 files
- Keep subject lines short and lowercasein 9 of 401, across 3 files
- Define ideal customer profile from top customersin 9 of 401, across 3 files
Said here and by no other author read
- use semicolon delimiter with no header row
- order columns member_id display_name email source
- build member_id from last name and row number
- zero-pad row number to four digits
- keep display_name as given
- lowercase email values
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.