AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Codebase Second Brain

skill-mallikarjun-roddannavar-playwright-agentic-automation-codebase-second-brain · by Mallikarjun-Roddannavar

Retrieve, verify, and refresh the persistent Open Knowledge Format v0.2 codebase memory for playwright-agentic-automation. Use when an agent needs architecture discovery, source ownership, page/API/fixture relationships, static AST graph queries, knowledge freshness checks, Mermaid/Obsidian navigation, or durable knowledge updates after repository changes.

↗ Repository
— No reviews yet
0 installs
15 views
0.0% view→install

Install

$ agentstack add skill-mallikarjun-roddannavar-playwright-agentic-automation-codebase-second-brain

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mallikarjun-roddannavar-playwright-agentic-automation-codebase-second-brain)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Codebase Second Brain? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Codebase Second Brain

Use knowledge/ as the first discovery layer. It is a portable, offline-first OKF v0.2 bundle; generated/ contains deterministic AST facts and architecture/, decisions/, and runbooks/ hold durable human-readable knowledge.

Retrieve Before Rediscovering

  1. Read knowledge/index.md.
  2. Run npm run knowledge:check. If it reports stale artifacts, treat the source code as authoritative and refresh before relying on generated facts.
  3. Run npm run knowledge:query -- .
  4. Open only the returned concept notes and their direct links. Read source only to verify an important claim, resolve a stale fact, or make the requested change.

Use --relation for exact relationship retrieval:

npm run knowledge:query -- --relation NAVIGATES_TO
npm run knowledge:query -- --relation USES_API_ROUTE
npm run knowledge:query -- --relation USES_FIXTURE

Windows Shell Fallback

If npm run knowledge:check hits the known Windows EPERM/realpath issue, run the underlying commands directly:

node ./scripts/buildKnowledge.mjs --check
node ./scripts/validateKnowledge.mjs

For a direct query, omit npm's extra delimiter: node ./scripts/queryKnowledge.mjs LoginPage.

Trust the Right Layer

  • Treat TypeScript source, config, and tests as authoritative.
  • Treat knowledge/generated/code-graph.json as machine-confirmed static analysis with source-hash provenance.
  • Do not describe graph edges as runtime behavior. They are static imports, declarations, resolved inheritance, concrete new expressions, type returns, route references, fixtures, and package usage.
  • Preserve unknown OKF frontmatter fields and tolerate broken Markdown links when consuming knowledge; do not silently invent missing facts.
  • Load references/static-graph-model.md only when changing the extractor or interpreting an edge type.

Refresh After a Relevant Change

When changing indexed TypeScript, JavaScript, JSON configuration, package metadata, or knowledge scripts:

  1. Run npm run knowledge:build.
  2. Run npm run knowledge:validate.
  3. Review the generated concepts, knowledge/generated/code-graph.json, and Mermaid graphs for factual changes.
  4. Keep the generated artifacts with the code change. Do not hand-edit files under knowledge/generated/.
  5. Add human reasoning, decisions, exceptions, and runbooks outside generated/, using valid OKF frontmatter with a non-empty type.

Obsidian

Open knowledge/ as an Obsidian vault when a visual link graph or Mermaid rendering is useful. Use normal Markdown links so the bundle stays portable to any Markdown/OKF consumer. Do not add user-specific .obsidian settings to the repository unless explicitly requested.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML