working-with-llm-context-rules

Fetches LLM context rule pods from controls and policies using the parent-walk pattern.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/fianulabs/fianu-skills --skill working-with-llm-context-rules-fianulabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: working-with-llm-context-rules
Source: https://github.com/fianulabs/fianu-skills/tree/main/skills/working-with-llm-context-rules
Command: npx skills add https://github.com/fianulabs/fianu-skills --skill working-with-llm-context-rules-fianulabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous decision workflows need explicit owner guidance before approving, denying, or escalating changes to controls and policies. This Skill standardizes how agents fetch the markdown guidance pods entity owners attach to those entities, and enforces a 0.70 confidence cap when no guidance exists. ## Core Features & Use Cases - Pod Fetch Contract: Defines the GET endpoints for listing all llm_context_rule pods on an entity and retrieving a specific pod's full markdown content by key. - Parent-Walk Pattern: When the target is a policy or policy_exception, also fetches the parent control's pod, preferring policy-level guidance for policy-specific decisions and control-level guidance for broader rules. - Confidence Cap Precondition: Establishes that missing pods on both target and parent cap decision confidence at 0.70, forcing advisory-only mode with a comment for human review. - Use Case: During an autonomous ticket approval, the agent fetches the policy's pod, finds guidance like "auto-deny any policy that removes the internet_facing index", and applies it to the decision. ## Quick Start Fetch the LLM context rule pods for this policy and its parent control, then tell me whether owner guidance exists or if we are capped at 0.70 confidence.

Frequently Asked Questions about working-with-llm-context-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch LLM context rule pods for a policy or control?▼

Call GET /pods/entities/{targetEntityId}?type=llm_context_rule to list all rule pods, then GET /pods/entities/{targetEntityId}/llm_context_rule/{key} to retrieve a specific pod's full markdown content.

What is the parent-walk pattern for policy guidance?▼

When the target is a policy or policy_exception, also fetch the parent control's LLM context rule pod. Policy-level pods take precedence for policy-specific decisions, while control-level pods provide broader guidance applying to all policies under that control.

What happens when no LLM context rule pod exists?▼

Decision confidence is capped at 0.70, putting the agent in advisory-only mode. The agent posts a comment for human review instead of taking autonomous action, and notes the advisory-only status in the decision comment.

Should fact-only analysis workflows load LLM context rules?▼

No. This skill is loaded only by autonomous decision workflows like managing-ticket-approvals. Fact-only workflows such as analyzing-tickets must not reference LLM context rules, as doing so violates that skill's contract.

How are pod fetch failures handled during decision workflows?▼

A 5xx fetch failure is treated as 'no pod found' for confidence purposes, so the 0.70 cap applies. The failure is logged distinctly so a human reviewer can investigate whether the pod was supposed to exist.