log-capability-gap

To log capability gaps, you state the attempted task, classify the missing type (such as data, tools, or permissions), estimate business impact, suggest an owner, and call the brain_capability_gap function to create tasks as needed.

You can classify and log capability gaps involving missing data, tools, permissions, skills, processes, or context that prevent agents or humans from completing work, ensuring these execution blockers are addressed.

Risk assessment during capability gap logging involves classifying the gap type and estimating its business impact, which helps prioritize task creation and suggest the appropriate owner or directly responsible individual.

The skill can suggest an owner and create tasks as needed for capability gaps, but it explicitly requires human oversight for sensitive or security-related gaps to ensure proper risk management.

The best way to report capability gaps is by calling brain_capability_gap, which logs the missing capability, classifies it, estimates impact, suggests an owner, and includes task paths in your responses.

Yes, a key limitation is that while the skill can log gaps and suggest owners, it requires direct human oversight for sensitive or security-related capability gaps to prevent automated mishandling of critical risks.