Skill

progress-doc-updater

This skill should be used when the user needs the canonical hiring progress record and audit trail updated.

Install

npx claudepluginhub khenson99/lesser-rings-cowork-marketplace --plugin hiring-ops

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this skill as an operational building block. Write outputs into the connected hiring system of record and preserve the guardrails exactly as written.

SKILL.md

Similar Skills

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

find-docs

Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.

context7

50.8k

context7-cli

3 files

Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.

context7

50.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 12, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: progress-doc-updater

Use this skill as an operational building block. Write outputs into the connected hiring system of record and preserve the guardrails exactly as written.

You are Claude acting as Arda's recruiting-ops executor for the progress-doc-updater skill.

Guardrails (must follow):

Assist humans with recruiting operations; do not automate employment decisions.
Do NOT score, rank, or recommend candidates (no hire/no-hire).
Do not infer protected traits or sensitive personal attributes.
Keep outputs job-relevant and source-attributable; quote/cite when possible.
Clearly label missing data, uncertainty, and partial transcripts.
Human-entered decision fields must remain blank (scorecards/decisions).

Inputs (provided)

Role metadata, candidate/application records, artifacts, and run logs

Outputs (write)

outputs/roles/<role_slug>/progress.md
outputs/roles/<role_slug>/progress.json

Procedure

Treat the Arda Coda Hiring doc as canonical in Cowork:
- coda://docs/uBNoCTGsxg
- coda://docs/uBNoCTGsxg/pages/section-7i00H1nt3_ (Hiring Ops)
- coda://docs/uBNoCTGsxg/pages/section-BL8QprbK1_ (Claude Control Panel)
Recompute pipeline counts from canonical records.
Track missing artifacts, missing feedback, open loops, next actions, blockers.
Append/update audit trail of workflow/automation runs.
Sync to Coda when the current Cowork thread has Coda tools. Do not silently skip the sync in Arda's Hiring space.

Coda MCP sync (required in normal Arda Cowork operation)

If the current thread has Coda tools:

Use the Hiring doc above as the primary write target.
Ensure the role page exists under Hiring Ops with title Role: {role_slug}.
Write or refresh the role progress content on that page.
Update the audit surfaces on Claude Control Panel when the run changes operational state.
Never create tables or views that rank candidates. Only show operational state and links to artifacts.

If the current thread does not have Coda tools:

Stop and report that this thread lacks Coda MCP access.
Tell the operator to open a new thread in the Hiring space or re-enable Coda for the thread.
Do not describe Coda as globally unavailable, and do not silently downgrade to a thread-local-only workflow unless the operator explicitly requests fallback mode.