agentsclimarketplace

Observability

Skill theinterneti/TTA.dev/.claude/skills/generated/observability

AI devops for vibe coders

Install
npx -y skills add theinterneti/TTA.dev --skill observability

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Observability subsystem in TTA.dev: demo_hierarchical_trace, handle_api_active_agents, handle_api_agent_actions and related code. 115 symbols | 38 files | Cohesion: 73%

SKILL.md

5.3 KB, ~1.4k tokens by cl100k_base, as published. Nobody here has run it

Observability

115 symbols | 38 files | Cohesion: 73%

When to Use

  • Working on observability-related functionality in TTA.dev
  • Modifying demo_hierarchical_trace, handle_api_active_agents
  • Navigating ttadev/observability/server.py, ttadev/observability/project_session.py

Key Files

FileSymbols
ttadev/observability/server.py_langfuse_creds, _estimate_cost, _v2_langfuse_session_cost, _v2_langfuse_scores, _init_state (+5)
tests/observability/test_span_pipeline.pytest_retry_succeeds_after_transient_failure, test_retry_exhausted_raises, test_retry_with_mock_primitive, test_cache_hit_skips_inner_primitive, _make_otel_span (+3)
ttadev/observability/project_session.pyjoin, get, get_by_id, add_member, assign_role (+2)
ttadev/observability/span_processor.pyfrom_activity_log, from_agent_tracker, extract_primitive_type, _normalize_provider, _parse_timestamp (+2)
ttadev/observability/agent_tracker.pytrack_agent_action, log_activity, get_active_agents, get_recent_actions, get_tracker (+1)
ttadev/primitives/observability/logging.py_log, debug, info, warning, error (+1)
ttadev/observability/session_manager.pyend_session_by_id, list_sessions, get_or_create_agent_session, update_session_project, _persist_session (+1)
ttadev/observability/auto_instrument.pylog_activity, log_tool_use, log_workflow_end, get_logger, log_workflow_start (+1)
tests/observability/test_handoff_tracing.py_free_port, test_dag_endpoint_empty_when_no_handoffs, test_dag_endpoint_returns_nodes_and_edges, _make_agent_spec, test_handoff_span_emitted_with_required_attributes (+1)
ttadev/observability/auto_track_copilot.pyis_copilot_session, get_copilot_context, wrapper, track_workflow_execution, track_agent_activation

Entry Points

Start here when exploring this area:

  • demo_hierarchical_trace (Function) — examples/demo_hierarchical_traces.py:8
  • handle_api_active_agents (Function) — ttadev/ui/observability_server.py:260
  • handle_api_agent_actions (Function) — ttadev/ui/observability_server.py:270
  • track_agent_action (Function) — ttadev/observability/agent_tracker.py:40
  • log_activity (Function) — ttadev/observability/agent_tracker.py:68

Key Symbols

SymbolTypeFileLine
demo_hierarchical_traceFunctionexamples/demo_hierarchical_traces.py8
handle_api_active_agentsFunctionttadev/ui/observability_server.py260
handle_api_agent_actionsFunctionttadev/ui/observability_server.py270
track_agent_actionFunctionttadev/observability/agent_tracker.py40
log_activityFunctionttadev/observability/agent_tracker.py68
get_active_agentsFunctionttadev/observability/agent_tracker.py107
get_recent_actionsFunctionttadev/observability/agent_tracker.py165
get_trackerFunctionttadev/observability/agent_tracker.py182
joinFunctionttadev/observability/project_session.py51
getFunctionttadev/observability/project_session.py58
get_by_idFunctionttadev/observability/project_session.py68
add_memberFunctionttadev/observability/project_session.py87
assign_roleFunctionttadev/observability/project_session.py96
mainFunctionexamples/demo_full_observability.py62
test_retry_succeeds_after_transient_failureFunctiontests/observability/test_span_pipeline.py234
test_retry_exhausted_raisesFunctiontests/observability/test_span_pipeline.py261
test_retry_with_mock_primitiveFunctiontests/observability/test_span_pipeline.py275
test_cache_hit_skips_inner_primitiveFunctiontests/observability/test_span_pipeline.py367
executeFunctionttadev/primitives/recovery/retry.py81
rootFunctionttadev/primitives/core/base.py217

Execution Flows

FlowTypeSteps
Control_list_project_ownership → Getcross_community5
Demo_hierarchical_trace → _update_registryintra_community4
Main → Get_loggercross_community4
Wrapper → _update_registrycross_community4
Track_workflow_execution → _update_registrycross_community4
Track_agent_activation → _update_registrycross_community4
Control_list_project_ownership → _create_project_session_managercross_community3
Control_list_session_ownership → Get_sessioncross_community3
Control_list_session_ownership → _create_session_managercross_community3
Wrapper → Get_trackercross_community3

Connected Areas

AreaConnections
Unit32 calls
Agents2 calls
Tools2 calls
Recovery1 calls
Control_plane1 calls

How to Explore

  1. gitnexus_context({name: "demo_hierarchical_trace"}) — see callers and callees
  2. gitnexus_query({query: "observability"}) — find related execution flows
  3. Read key files listed above for implementation details

Gives 0 of the 12 instructions most monitoring observability skills give in ~1.4k tokens

Counted across 481 of the 483 authors here whose files we hold, read 2026-08-06

  • link every alert to a runbookin 43 of 481, across 35 files
  • use structured json loggingin 36 of 481, across 31 files
  • alert on user-facing symptomsin 20 of 481, across 15 files
  • emit structured JSON logs with stable event namesin 18 of 481, across 13 files
  • propagate trace context across boundariesin 16 of 481
  • use histograms for latency trackingin 14 of 481, across 9 files
  • use OpenTelemetry for distributed tracingin 13 of 481, across 8 files
  • include a correlation ID on every log linein 13 of 481, across 8 files
  • Define service level objectivesin 10 of 481, across 7 files
  • Call useAzureMonitor before importing other modulesin 9 of 481, across 2 files
  • stop and ask for clarification if inputs are missingin 9 of 481, across 2 files
  • define on-call questions before adding telemetryin 9 of 481, across 4 files

Said here and by no other author read

  • Explore execution flows
  • Read key files for implementation details

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.