sitemap-task-bias
Use when creating or auditing an agent-team sitemap, Task Bias ledger, concept coverage, product surface map, validation chain, or missing-concept check.
Profile →npx skills add agentlas-ai/Agentlas-OS --skill sitemap-task-bias --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Sitemap Task Bias ## Procedure 1. List the user-facing surfaces, workflows, agent roles, skills, memory scopes, runtime adapters, policy gates, and verification lanes. 2. Compare the request against required concept coverage: - sitemap; - PM Soul; - memory architecture; - all-LLM runtime architecture; - public/private boundary; - install and verification path. 3. Add task biases that protect the build from dropping important concerns. 4. Record skipped or blocked concepts in `.agentlas/validation-ledger.jsonl`. ## Output Return `covered`, `missing`, `task_biases`, and `evidence_files`.
- Procedure
- Output
What does the sitemap-task-bias skill do?
Use when creating or auditing an agent-team sitemap, Task Bias ledger, concept coverage, product surface map, validation chain, or missing-concept check.
How do I install it?
Run `npx skills add agentlas-ai/Agentlas-OS --skill sitemap-task-bias --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentlas-ai/Agentlas-OS, a repository with 1,165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.