Update to trackly
Snapshot Oct 25, 2026 · 19:02 UTC · version 1.0.7
Collection source: downloaded plugin package.
Instructions updated for trackly
Skill instructions — Now says: Do not rescore an approved application inside this discovery skill. When the user asks to finish Apply setup, resolve missing profile or resume requirements,...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 24, 2026 · 13:47 UTC
Do not rescore an approved application inside this discovery skill. When the user asks to fill an approved application, use the `trackly-apply` skill.
Oct 25, 2026 · 19:02 UTC
Do not rescore an approved application inside this discovery skill. When the user asks to finish Apply setup, resolve missing profile or resume requirements, or fill an approved application, use the `trackly-apply` skill.
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -16,7 +16,7 @@ 5. Present returned facts as returned by trackly. Label any model inference as an inference and never imply a posting is still open when trackly reports otherwise. 6. Call `trackly_update_status` only after the user chooses a job or explicitly asks to update its status. Marking a job `applied` additionally requires Apply write permission because it reconciles the application run; never use it to infer or claim submission. -Do not rescore an approved application inside this discovery skill. When the user asks to fill an approved application, use the `trackly-apply` skill. +Do not rescore an approved application inside this discovery skill. When the user asks to finish Apply setup, resolve missing profile or resume requirements, or fill an approved application, use the `trackly-apply` skill. ## Scope boundary
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: trackly\ndescription: Search trackly for current jobs and companies, inspect job briefs and preferences, and save only the jobs the user chooses. Use when the user asks to find, compare, inspect, or track job openings.\n---\n\n# trackly\n\nUse trackly as the source of truth for current openings, monitored companies, saved jobs, and discovery preferences.\n\n## Search workflow\n\n1. If the request depends on saved preferences, call `trackly_get_preferences` before searching. Do not invent a preference that is missing.\n2. Call `trackly_search_jobs` with the user's explicit constraints. Preserve recency, location, remote, company, and role constraints exactly.\n3. Use `trackly_search_companies` only when company discovery or company identity is part of the request.\n4. Use `trackly_get_job` for the exact posting record and `trackly_get_job_brief` for a decision-ready summary. Treat `postedLast7d` and `latestPostedAt` as validated posting-date signals only; never substitute first-seen time for a posting date.\n5. Present returned facts as returned by trackly. Label any model inference as an inference and never imply a posting is still open when trackly reports otherwise.\n6. Call `trackly_update_status` only after the user chooses a job or explicitly asks to update its status. Marking a job `applied` additionally requires Apply write permission because it reconciles the application run; never use it to infer or claim submission.\n\nDo not rescore an approved application inside this discovery skill. When the user asks to fill an approved application, use the `trackly-apply` skill.\n\n## Scope boundary\n\nThis plugin supports job and company search, job briefs, tracking, and application filling. Employee discovery and referral intelligence are outside its scope.\n"
"---\nname: trackly\ndescription: Search trackly for current jobs and companies, inspect job briefs and preferences, and save only the jobs the user chooses. Use when the user asks to find, compare, inspect, or track job openings.\n---\n\n# trackly\n\nUse trackly as the source of truth for current openings, monitored companies, saved jobs, and discovery preferences.\n\n## Search workflow\n\n1. If the request depends on saved preferences, call `trackly_get_preferences` before searching. Do not invent a preference that is missing.\n2. Call `trackly_search_jobs` with the user's explicit constraints. Preserve recency, location, remote, company, and role constraints exactly.\n3. Use `trackly_search_companies` only when company discovery or company identity is part of the request.\n4. Use `trackly_get_job` for the exact posting record and `trackly_get_job_brief` for a decision-ready summary. Treat `postedLast7d` and `latestPostedAt` as validated posting-date signals only; never substitute first-seen time for a posting date.\n5. Present returned facts as returned by trackly. Label any model inference as an inference and never imply a posting is still open when trackly reports otherwise.\n6. Call `trackly_update_status` only after the user chooses a job or explicitly asks to update its status. Marking a job `applied` additionally requires Apply write permission because it reconciles the application run; never use it to infer or claim submission.\n\nDo not rescore an approved application inside this discovery skill. When the user asks to finish Apply setup, resolve missing profile or resume requirements, or fill an approved application, use the `trackly-apply` skill.\n\n## Scope boundary\n\nThis plugin supports job and company search, job briefs, tracking, and application filling. Employee discovery and referral intelligence are outside its scope.\n"
Full snapshot data
{
"description": "Search trackly for current jobs and companies, inspect job briefs and preferences, and save only the jobs the user chooses. Use when the user asks to find, compare, inspect, or track job openings.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 500
}
],
"name": "trackly",
"skill_md_contents": "---\nname: trackly\ndescription: Search trackly for current jobs and companies, inspect job briefs and preferences, and save only the jobs the user chooses. Use when the user asks to find, compare, inspect, or track job openings.\n---\n\n# trackly\n\nUse trackly as the source of truth for current openings, monitored companies, saved jobs, and discovery preferences.\n\n## Search workflow\n\n1. If the request depends on saved preferences, call `trackly_get_preferences` before searching. Do not invent a preference that is missing.\n2. Call `trackly_search_jobs` with the user's explicit constraints. Preserve recency, location, remote, company, and role constraints exactly.\n3. Use `trackly_search_companies` only when company discovery or company identity is part of the request.\n4. Use `trackly_get_job` for the exact posting record and `trackly_get_job_brief` for a decision-ready summary. Treat `postedLast7d` and `latestPostedAt` as validated posting-date signals only; never substitute first-seen time for a posting date.\n5. Present returned facts as returned by trackly. Label any model inference as an inference and never imply a posting is still open when trackly reports otherwise.\n6. Call `trackly_update_status` only after the user chooses a job or explicitly asks to update its status. Marking a job `applied` additionally requires Apply write permission because it reconciles the application run; never use it to infer or claim submission.\n\nDo not rescore an approved application inside this discovery skill. When the user asks to finish Apply setup, resolve missing profile or resume requirements, or fill an approved application, use the `trackly-apply` skill.\n\n## Scope boundary\n\nThis plugin supports job and company search, job briefs, tracking, and application filling. Employee discovery and referral intelligence are outside its scope.\n"
}SHA-256 of public snapshot: 0b003ff3ca63858ca7e8c6492cd4a4608646f9ac7e1327753e2e4767876f2a6b