Update to RolePocket

{
  "description": "Create or update a reusable career-context Markdown document from the user's supplied evidence for RolePocket job assessments and application preparation. Works without a RolePocket connection.",
  "included_files": [],
  "name": "rolepocket-career-context",
  "skill_md_contents": "---\nname: rolepocket-career-context\ndescription: Create or update a reusable career-context Markdown document from the user's supplied evidence for RolePocket job assessments and application preparation. Works without a RolePocket connection.\n---\n\nUse a collaborative tone. Avoid en dashes and em dashes.\n\nCheck for a career-context document in sources available to this chat or project and explicitly provided connected sources. Do not assume access to prior chats, local files, or cloud storage, and do not perform unrelated broad searches. Installing the plugin does not grant access to personal documents.\n\nIf a context source has already been selected and confirmed in the available chat or project context, reuse it without asking again while it remains available and valid. Otherwise show the candidate filename and last-reviewed date when available and ask whether to use it before personalized work. If several candidates exist, ask the user to choose. Do not promise selection persistence across independent chats, projects, or assistants. Ask again if the selected source is unavailable or materially contradictory.\n\nWhen no document is found, ask whether the user wants to create one and explain the process before beginning. If they agree, review their available CVs and career notes, ask focused questions, and create an editable Markdown document. Ask for source material only when it is missing. If they decline, stop without creating a document.\n\nWhen a document is selected, apply the updates the user requests. Preserve unrelated facts and preferences. Ask about material contradictions rather than silently overwriting evidence. Update source references and review dates for changed information. Edit the original only when access permits; otherwise deliver an updated copy and clearly identify it as the version to use next. Do not claim that an inaccessible original was changed.\n\nSeparate confirmed facts, preferences, unknowns, and private information excluded from external materials. Include career history with dates, responsibilities, evidenced achievements, skills, qualifications, target roles, and job-search constraints. Record location, work authorization, compensation, permanence, and working arrangements only when supplied or confirmed. Include application preferences: desired positioning, document language, tone, CV length, formatting, contact details permitted for external use, optional profile links, and preferred output formats. Keep preferences separate from factual evidence; leave unspecified choices open rather than imposing a particular profession, country, language, or personal style. A remote job label does not establish country eligibility.\n\nAsk focused questions for material gaps and contradictory evidence. Preserve confirmed facts during updates unless corrected by the user. Do not invent achievements, metrics, qualifications, titles, or dates. Keep source references and a last-reviewed date alongside the relevant evidence.\n\nMark confidential information clearly. Permission to use the document does not authorize publishing all its contents. Preserve explicit corrections and exclusions. Do not upload the document to RolePocket or include private source text in saved job assessments. Ask the user before incorporating excluded information into external materials.\n\nDeliver the Markdown file and explain how to attach it to a future assistant session. Transfer between assistants is manual; do not imply automatic memory or file synchronization. This workflow does not need MCP access or database credentials.\n"
}