lark-doc

Name: lark-doc
Rating: 7.7 (54 reviews)
Author: XiaoMi

by XiaoMi1.1k178GitHub

This skill fetches Lark/Feishu documents and converts them to Markdown format, plus appends structured troubleshooting summaries. It's designed for teams using Lark for documentation who need to access guides and record issue resolutions programmatically.

Output Preview

output_preview.md

# Database Connection Troubleshooting Guide

## Common Issues

### Issue 1: Connection Timeout

**Symptoms:**
- Application logs show "Connection timed out"
- Database monitoring shows high connection count

**Resolution Steps:**
1. Check network connectivity between application and database
2. Verify firewall rules allow traffic on port 5432
3. Review database connection pool settings
4. Check for long-running queries blocking connections

### Issue 2: Authentication Failure

**Symptoms:**
- "FATAL: password authentication failed" in logs
- Application cannot establish initial connection

**Resolution Steps:**
1. Verify credentials in environment variables
2. Check password expiration policy
3. Confirm user has correct permissions
4. Test connection with psql CLI

---

### Database Replication Lag (2025-01-15 14:30)

#### Problem Description

Primary database showing 15-minute replication lag to standby replica. Monitoring alerts triggered for lag exceeding 10 minutes threshold.

#### Troubleshooting Steps

- Checked WAL shipping status: streaming active but slow
- Verified network bandwidth: 100Mbps connection saturated
- Reviewed pg_stat_replication: write_lag = 00:15:22.456
- Checked replica disk I/O: high write latency on EBS volume

#### Solution

Increased EBS volume size from gp2 100GB to gp3 500GB with 3000 IOPS. Replication lag reduced to 30 seconds within 10 minutes.

#### Notes

Consider setting up monitoring for disk I/O metrics on replicas. Plan to implement read replicas for reporting workloads.

Target Audience

DevOps engineers and support teams who use Lark/Feishu for documentation and need to automate access to troubleshooting guides

10/10Security

Low security risk, safe to use

Clarity

Practicality

Quality

Maintainability

Innovation

Documentation

lark-apimarkdown-convertertroubleshootingknowledge-basefeishu

Compatible Agents

Claude Code

~/.claude/skills/

Codex CLI

~/.codex/skills/

Gemini CLI

~/.gemini/skills/

OpenCode

~/.opencode/skills/

OpenClaw

~/.openclaw/skills/

GitHub Copilot

~/.copilot/skills/

Cursor

~/.cursor/skills/

Windsurf

~/.codeium/windsurf/skills/

Cline

~/.cline/skills/

Roo Code

~/.roo/skills/

Kiro

~/.kiro/skills/

Junie

~/.junie/skills/

Augment Code

~/.augment/skills/

Warp

~/.warp/skills/

Goose

~/.config/goose/skills/

SKILL.md

Lark Document Skill

This skill provides two capabilities:

Fetch a Lark (Feishu) document and convert its content to Markdown format
Append troubleshooting summaries to the document for future reference

When to Use

Fetch Document:

User needs troubleshooting steps or operation guides
Before diagnosing issues, check if there are relevant operation instructions
When user asks about specific procedures or step-by-step guides
Keywords: troubleshooting, steps, guide, procedure, operation, how to fix

Append Summary:

After completing a troubleshooting session
When user wants to document a resolved issue for future reference
To add new troubleshooting cases to the guide document
Keywords: save, record, document, write summary, add to guide

How to Use

Fetch Document

uv run python .claude/skills/lark-doc/fetch_doc.py

Append Troubleshooting Summary

uv run python .claude/skills/lark-doc/append_summary.py \
  -t "问题标题" \
  -p "问题描述" \
  -s '["排查步骤1", "排查步骤2", "排查步骤3"]' \
  -o "解决方案" \
  -n "可选备注"

Parameters:

-t, --title: Title of the troubleshooting case (required)
-p, --problem: Description of the problem (required)
-s, --steps: JSON array of troubleshooting steps taken (required)
-o, --solution: The solution that resolved the issue (required)
-n, --notes: Optional additional notes

Environment Variables

LARK_APP_ID: Lark application ID
LARK_APP_SECRET: Lark application secret
LARK_DOC_URL: The Lark document URL to fetch/append to
LARK_DOMAIN: (Optional) Custom domain for enterprise Lark

Output Format

Fetch Document

Returns Markdown formatted content of the Lark document, including:

Headings (H1-H9)
Text paragraphs
Ordered and unordered lists
Code blocks
Quotes
Todo items (checkboxes)

Append Summary

Returns JSON with success status:

{
  "success": true,
  "documentId": "xxx",
  "url": "https://...",
  "message": "Successfully appended troubleshooting summary: ..."
}

Example Output

Fetched Document

# Troubleshooting Guide

## Common Issues

### Issue 1: Service Not Starting

1. Check the logs
2. Verify configuration
3. Restart the service

### Issue 2: Connection Timeout

- Check network connectivity
- Verify firewall rules

Appended Summary Structure

The summary will be appended to the document with the following structure:

---

### 问题标题 (2025-01-15 14:30)

#### 问题描述

问题的详细描述...

#### 排查步骤

- 排查步骤1
- 排查步骤2
- 排查步骤3

#### 解决方案

解决方案的详细说明...

#### 备注

可选的备注信息...

Source: https://github.com/XiaoMi/mone#jcommon~mcp~mcp-smartsre~.claude~skills~lark-doc

Content curated from original sources, copyright belongs to authors

Grade A

7.7AI Score

Best Practices

Checking...

Try this Skill

User Rating

USER RATING

0UP

0DOWN

Loading files...

WORKS WITH

Claude

Codex

Gemini