SKILLEMALL.ai
GitHub ↗ RU Sign in

CF career-ops-plugin-notion

How to mirror the career-ops tracker to a Notion database and read records back as job leads.

The skillemall take

Promises to sync your career tracker with Notion and pull job leads from it. Four files with instructions and two scripts inside. Checks found no critical issues, but code quality scored 63, process logic 31. Translation: the approach works, implementation is rough. Safety at 100, so it won't break things. Install if you're ready to adapt scripts to your Notion structure and job schema. Good enough for a quick push to Notion. Not ready for production use without rework.

career-ops-hq/career-ops Agent Skills author: career-ops-hq MIT 4 files · 2 scripts body ≈ 261 tokens Open the sourcegithub.com↗ analyzed 5 d ago

How to mirror the career-ops tracker to a Notion database and read records back as job leads.

As a process F 31/100 · No process to follow — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureNotionInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
F
31/100
No process to follow
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: career-ops-plugin-notion (santifer/career-ops)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 31/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (career-ops-plugin-notion) differs from the folder (notion)
  • 50Steps. 2 steps
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 100Execution cost. Instruction body is 261 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 93: 120–800 characters recommended
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +4Structure: 4 headings
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.