← SeekrlyCONTENT HISTORY

Update to Seekrly

Snapshot Nov 1, 2026 · 18:10 UTC · version 1.2.1

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for seekrly-career-profile

Full description — Now says: projects, job preferences (roles, salary, locations, notice period) and facts about the user.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Seekrly and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Full description

Before

Oct 24, 2026 · 13:52 UTC

projects and job preferences (roles, salary, locations, notice period).

After

Nov 1, 2026 · 18:10 UTC

projects, job preferences (roles, salary, locations, notice period) and facts about the user.

Skill instructions

Before

Oct 24, 2026 · 13:52 UTC

projects and job preferences (roles, salary, locations, notice period). Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share. `shiftPreference`, `jo...

After

Nov 1, 2026 · 18:10 UTC

projects, job preferences (roles, salary, locations, notice period) and facts about the user. Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share. ...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 ---
 name: seekrly-career-profile
-description: Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects and job preferences (roles, salary, locations, notice period). Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share.
+description: Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects, job preferences (roles, salary, locations, notice period) and facts about the user. Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share.
 ---
 
 # Career profile
@@ -14,9 +14,12 @@
 `skills`, `projects`, `certificates`, `awards`, `languages`, `volunteer`,
 `publications`, `interests`, `references`) plus `jobPreferences`
 (`preferredRole`, `yearsExperience`, `currentCtc`, `expectedCtc`, `employmentType`,
-`shiftPreference`, `jobType`, `preferredLocations`, `noticePeriod` in days).
+`shiftPreference`, `jobType`, `preferredLocations`, `noticePeriod` in days) and
+`facts`: free-text notes the user wants Seekrly AI and autofill to know (e.g.
+"Needs visa sponsorship for the US"). Follow them when you write for the user.
+Each project has `links` (`{ name, url }`, e.g. "Live", "GitHub"), not one `url`.
 
-## Updating (two-step)
+## Updating
 
 1. **Always read first** with `get_career_profile`.
 2. Build the change with the same field names:
@@ -24,14 +27,16 @@
      merge. `profiles` replaces the whole list of links. Phone format:
      `+<country code> <number>`.
    - `jobPreferences`: fields passed replace those preferences; others stay.
+   - `facts`: replaces the whole list. To add one, send the existing facts plus
+     the new one.
    - **Sections replace the whole section.** To add one job, send the complete
      `work` list: existing entries plus the new one. Never send a partial list
      unless the user wants entries removed.
 3. Show the change in the chat first (each field or section, before → after)
-   and ask "Update it, or change something?"
-4. After a yes, call `update_career_profile` without a token: you get a before/after preview and
-   a warning (it flags sections that would lose entries). Show it to the user.
-5. Only if they agree, repeat the identical call with `confirmationToken`.
+   and ask "Update it, or change something?" Say plainly if a section will lose
+   entries: removed entries can't be restored.
+4. After a yes, call `update_career_profile` once. It saves right away; don't ask
+   again.
 
 Not editable here: `basics.name`, `basics.email`, the photo, gender and date of
 birth - the user changes those on the Seekrly Profile page.
@@ -39,13 +44,18 @@
 ## Filling the profile from a resume or details
 
 If the user just tells you the details, map them to the sections above and
-follow the two-step update. For a resume:
+follow the update steps above. Anything about the user that fits no field (work
+authorization or visa status, availability to start, willingness to relocate or
+travel, driving licence, security clearance) goes in `facts`, one short
+sentence each, added to the existing facts; never put something there that fits
+another field. For a resume:
 
 1. Ask the user to attach their resume (PDF or DOCX) or paste its text.
 2. Read the whole file and map it to the sections above: dates `YYYY-MM`, bullets
-   into `highlights`, skills grouped with `keywords`. Copy facts exactly; leave
-   out anything the resume doesn't say.
+   into `highlights`, skills grouped with `keywords`, a project's links into
+   `links`. Details about the user with no field go in `facts` (see above).
+   Copy everything exactly; leave out anything the resume doesn't say.
 3. Compare with `get_career_profile` and show what would be added or replaced.
    Keep existing entries unless the resume clearly replaces them (a section
    replaces its whole list).
-4. Follow the two-step update above.
+4. Follow the update steps above.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects and job preferences (roles, salary, locations, notice period). Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share."
AFTER
"Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects, job preferences (roles, salary, locations, notice period) and facts about the user. Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share."

changed /skill_md_contents

BEFORE
"---\nname: seekrly-career-profile\ndescription: Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects and job preferences (roles, salary, locations, notice period). Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share.\n---\n\n# Career profile\n\nFollow the ground rules in the `seekrly` skill. The profile feeds Seekrly's resumes,\nautofill and job matching, so only save facts the user confirmed.\n\n## Reading\n\n`get_career_profile` returns JSON Resume sections (`basics`, `work`, `education`,\n`skills`, `projects`, `certificates`, `awards`, `languages`, `volunteer`,\n`publications`, `interests`, `references`) plus `jobPreferences`\n(`preferredRole`, `yearsExperience`, `currentCtc`, `expectedCtc`, `employmentType`,\n`shiftPreference`, `jobType`, `preferredLocations`, `noticePeriod` in days).\n\n## Updating (two-step)\n\n1. **Always read first** with `get_career_profile`.\n2. Build the change with the same field names:\n   - `basics`: only the fields passed change; `null` clears one. `location` fields\n     merge. `profiles` replaces the whole list of links. Phone format:\n     `+<country code> <number>`.\n   - `jobPreferences`: fields passed replace those preferences; others stay.\n   - **Sections replace the whole section.** To add one job, send the complete\n     `work` list: existing entries plus the new one. Never send a partial list\n     unless the user wants entries removed.\n3. Show the change in the chat first (each field or section, before → after)\n   and ask \"Update it, or change something?\"\n4. After a yes, call `update_career_profile` without a token: you get a before/after preview and\n   a warning (it flags sections that would lose entries). Show it to the user.\n5. Only if they agree, repeat the identical call with `confirmationToken`.\n\nNot editable here: `basics.name`, `basics.email`, the photo, gender and date of\nbirth - the user changes those on the Seekrly Profile page.\n\n## Filling the profile from a resume or details\n\nIf the user just tells you the details, map them to the sections above and\nfollow the two-step update. For a resume:\n\n1. Ask the user to attach their resume (PDF or DOCX) or paste its text.\n2. Read the whole file and map it to the sections above: dates `YYYY-MM`, bullets\n   into `highlights`, skills grouped with `keywords`. Copy facts exactly; leave\n   out anything the resume doesn't say.\n3. Compare with `get_career_profile` and show what would be added or replaced.\n   Keep existing entries unless the resume clearly replaces them (a section\n   replaces its whole list).\n4. Follow the two-step update above.\n"
AFTER
"---\nname: seekrly-career-profile\ndescription: Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects, job preferences (roles, salary, locations, notice period) and facts about the user. Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share.\n---\n\n# Career profile\n\nFollow the ground rules in the `seekrly` skill. The profile feeds Seekrly's resumes,\nautofill and job matching, so only save facts the user confirmed.\n\n## Reading\n\n`get_career_profile` returns JSON Resume sections (`basics`, `work`, `education`,\n`skills`, `projects`, `certificates`, `awards`, `languages`, `volunteer`,\n`publications`, `interests`, `references`) plus `jobPreferences`\n(`preferredRole`, `yearsExperience`, `currentCtc`, `expectedCtc`, `employmentType`,\n`shiftPreference`, `jobType`, `preferredLocations`, `noticePeriod` in days) and\n`facts`: free-text notes the user wants Seekrly AI and autofill to know (e.g.\n\"Needs visa sponsorship for the US\"). Follow them when you write for the user.\nEach project has `links` (`{ name, url }`, e.g. \"Live\", \"GitHub\"), not one `url`.\n\n## Updating\n\n1. **Always read first** with `get_career_profile`.\n2. Build the change with the same field names:\n   - `basics`: only the fields passed change; `null` clears one. `location` fields\n     merge. `profiles` replaces the whole list of links. Phone format:\n     `+<country code> <number>`.\n   - `jobPreferences`: fields passed replace those preferences; others stay.\n   - `facts`: replaces the whole list. To add one, send the existing facts plus\n     the new one.\n   - **Sections replace the whole section.** To add one job, send the complete\n     `work` list: existing entries plus the new one. Never send a partial list\n     unless the user wants entries removed.\n3. Show the change in the chat first (each field or section, before → after)\n   and ask \"Update it, or change something?\" Say plainly if a section will lose\n   entries: removed entries can't be restored.\n4. After a yes, call `update_career_profile` once. It saves right away; don't ask\n   again.\n\nNot editable here: `basics.name`, `basics.email`, the photo, gender and date of\nbirth - the user changes those on the Seekrly Profile page.\n\n## Filling the profile from a resume or details\n\nIf the user just tells you the details, map them to the sections above and\nfollow the update steps above. Anything about the user that fits no field (work\nauthorization or visa status, availability to start, willingness to relocate or\ntravel, driving licence, security clearance) goes in `facts`, one short\nsentence each, added to the existing facts; never put something there that fits\nanother field. For a resume:\n\n1. Ask the user to attach their resume (PDF or DOCX) or paste its text.\n2. Read the whole file and map it to the sections above: dates `YYYY-MM`, bullets\n   into `highlights`, skills grouped with `keywords`, a project's links into\n   `links`. Details about the user with no field go in `facts` (see above).\n   Copy everything exactly; leave out anything the resume doesn't say.\n3. Compare with `get_career_profile` and show what would be added or replaced.\n   Keep existing entries unless the resume clearly replaces them (a section\n   replaces its whole list).\n4. Follow the update steps above.\n"
Full snapshot data
{
  "description": "Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects, job preferences (roles, salary, locations, notice period) and facts about the user. Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share.",
  "included_files": [],
  "name": "seekrly-career-profile",
  "skill_md_contents": "---\nname: seekrly-career-profile\ndescription: Read and update the user's Seekrly career profile - headline, summary, contact details, links, work history, education, skills, projects, job preferences (roles, salary, locations, notice period) and facts about the user. Use when the user wants to update their profile, add a new job or skill, change job preferences, or fill the profile from a resume they share.\n---\n\n# Career profile\n\nFollow the ground rules in the `seekrly` skill. The profile feeds Seekrly's resumes,\nautofill and job matching, so only save facts the user confirmed.\n\n## Reading\n\n`get_career_profile` returns JSON Resume sections (`basics`, `work`, `education`,\n`skills`, `projects`, `certificates`, `awards`, `languages`, `volunteer`,\n`publications`, `interests`, `references`) plus `jobPreferences`\n(`preferredRole`, `yearsExperience`, `currentCtc`, `expectedCtc`, `employmentType`,\n`shiftPreference`, `jobType`, `preferredLocations`, `noticePeriod` in days) and\n`facts`: free-text notes the user wants Seekrly AI and autofill to know (e.g.\n\"Needs visa sponsorship for the US\"). Follow them when you write for the user.\nEach project has `links` (`{ name, url }`, e.g. \"Live\", \"GitHub\"), not one `url`.\n\n## Updating\n\n1. **Always read first** with `get_career_profile`.\n2. Build the change with the same field names:\n   - `basics`: only the fields passed change; `null` clears one. `location` fields\n     merge. `profiles` replaces the whole list of links. Phone format:\n     `+<country code> <number>`.\n   - `jobPreferences`: fields passed replace those preferences; others stay.\n   - `facts`: replaces the whole list. To add one, send the existing facts plus\n     the new one.\n   - **Sections replace the whole section.** To add one job, send the complete\n     `work` list: existing entries plus the new one. Never send a partial list\n     unless the user wants entries removed.\n3. Show the change in the chat first (each field or section, before → after)\n   and ask \"Update it, or change something?\" Say plainly if a section will lose\n   entries: removed entries can't be restored.\n4. After a yes, call `update_career_profile` once. It saves right away; don't ask\n   again.\n\nNot editable here: `basics.name`, `basics.email`, the photo, gender and date of\nbirth - the user changes those on the Seekrly Profile page.\n\n## Filling the profile from a resume or details\n\nIf the user just tells you the details, map them to the sections above and\nfollow the update steps above. Anything about the user that fits no field (work\nauthorization or visa status, availability to start, willingness to relocate or\ntravel, driving licence, security clearance) goes in `facts`, one short\nsentence each, added to the existing facts; never put something there that fits\nanother field. For a resume:\n\n1. Ask the user to attach their resume (PDF or DOCX) or paste its text.\n2. Read the whole file and map it to the sections above: dates `YYYY-MM`, bullets\n   into `highlights`, skills grouped with `keywords`, a project's links into\n   `links`. Details about the user with no field go in `facts` (see above).\n   Copy everything exactly; leave out anything the resume doesn't say.\n3. Compare with `get_career_profile` and show what would be added or replaced.\n   Keep existing entries unless the resume clearly replaces them (a section\n   replaces its whole list).\n4. Follow the update steps above.\n"
}

SHA-256 of public snapshot: 3f7a11caaa0252e82aaab0e81f31bfb88903a5b55cf23b5fa63e7eb4a3ff7b7a